SleekView Kanban for wpDiscuz
SleekView Kanban reads your wpDiscuz comments straight from the comments table, groups them into Approved, Pending, Spam, and Trash columns, and lets your moderators drag cards between lanes to clear the queue without bouncing between WordPress admin filter views.
♾️ Lifetime License available
Why a kanban view fits wpDiscuz moderation
wpDiscuz uses the standard WordPress comments table, wp_comments, where the comment_approved column holds the status: 1 for approved, 0 for pending, the string spam for spam, and trash for trashed comments. wpDiscuz adds extra meta for likes, reports, and rating values on top, but the moderation column itself is the same one the WordPress core comments screen uses for every site.
SleekView Kanban reads wp_comments filtered to wpDiscuz threads, groups rows by comment_approved, and renders one card per comment. Card fronts show the author display name, a short excerpt from comment_content, the post title the comment was left under, the like count from wpDiscuz meta, and the time since the comment was posted, which is enough to decide on most comments without leaving the board.
Dragging a card to Approved calls wp_set_comment_status() with the matching status, dragging to Spam calls wp_spam_comment(), and dragging to Trash calls wp_trash_comment(). The wpDiscuz hooks tied to those WordPress comment functions keep firing as before, so reply counts, frontend rendering, and any custom code already listening continue to behave the same way they do on the standard admin screen.
Workflow
Build a wpDiscuz comment board in four steps
Connect SleekView to wpDiscuz
Pick the comment_approved column
Choose what shows on each card
Enable drag-and-drop comment moderation
Sample board
Sample wpDiscuz comment moderation board
Comparison
Default wpDiscuz vs SleekView Kanban
Default WordPress comments screen
- The WordPress comments admin treats each status as a separate filter tab, not a side by side board.
- Pending and reported comments live behind extra clicks instead of being visible all at once.
- Comment moderation actions are row hovers, which slow down the work during a spam wave.
- There is no shared queue view for moderators clearing comments across many posts at once.
- wpDiscuz reports and likes only appear after clicking each comment, not on the moderation list.
SleekView Kanban
-
Group
wp_commentsrows bycomment_approvedacross Approved, Pending, Spam, and Trash. - Card fronts show author, excerpt, post title, like count, and report count without extra clicks.
-
Dragging to Spam calls
wp_spam_comment()so the WordPress hooks fire as normal. - Pending and reported columns can be split into two lanes for richer triage workflows.
- Per-post and per-category boards keep moderation focused on the team that owns the section.
Features
What SleekView Kanban gives you for wpDiscuz
All comment states in one board
Approved, Pending, Spam, and Trash sit in one board with live counts, so the moderation team sees how many comments are waiting in each state. Spam waves become obvious because the Spam column grows quickly, and the team can react before the comments thread is overrun with junk.
Drag uses WordPress comment functions
Moving a card calls wp_set_comment_status, wp_spam_comment, or wp_trash_comment, which means every wpDiscuz hook and every notification keeps firing the same way it does from the standard admin. There is no separate moderation path that could drift from the WordPress comment pipeline.
Per-post and per-category boards
Boards can be scoped to a single post, a category, or sitewide, with per-role permissions on top. This means a section editor only sees comments under their section, while a site moderator runs a wider board across all posts, and both teams share the same drag-and-drop workflow.
Audience
wpDiscuz teams running comment moderation on a board
News and blog sites with active comments
News sites get bursts of comments after each lead story. The board makes the burst visible because the Pending column grows quickly, and the moderation team can clear it in one focused pass before the next article goes live, instead of trickling through one filter at a time.
Course blogs with student comments
Course blogs use comments for student questions on each lesson. The board lets the course team approve student questions in batches, spam any obvious abuse, and trash duplicates. Approved questions then turn into a transcript of what students were stuck on each week.
Niche review sites with reader replies
Review sites get long, thoughtful replies that need a human read. The board's Pending column gives that work a clear home, and reviewers can sort by report count to catch any abusive comments at the top of the column without scrolling through approved replies.
The bigger picture
Why wpDiscuz benefits from a board even on a single-author blog
wpDiscuz is what makes comments feel like a conversation again. Threading, likes, reports, and inline replies all turn the comments section into something readers want to come back to. But the conversation only stays alive if comments get approved fast, spam gets cleared fast, and pending comments do not pile up while the author is busy.
The default WordPress comments screen is fine for a quiet blog, but as soon as the site picks up readers, the screen turns into a long list with filters that hide the work. A kanban board changes that. The Pending column becomes the inbox the author or moderator clears every morning, the Spam column shows the size of the spam wave, and the Trash column keeps the audit trail for anything removed during cleanup.
Because the Approved column is right next to the others, the moderator gets a constant sense of the size of the live conversation, which is helpful when deciding whether to write a follow-up post or pin a top comment. On a small site, a board keeps comments fresh and welcoming. On a large site, it stops moderation from becoming a part-time job nobody volunteers for, and that is exactly the kind of long-term care that makes a comment culture worth having.
Questions
Common questions about SleekView Kanban for wpDiscuz
It calls the WordPress comment functions. SleekView never writes to wp_comments directly for moderation actions. wp_set_comment_status, wp_spam_comment, and wp_trash_comment run through the standard pipeline, so all wpDiscuz hooks and email notifications continue to fire as before.
Yes. SleekView reads the wpDiscuz reports meta and can group cards by report count or by a derived status flag, so reported comments sit in their own column with a live count. This lets the moderation team prioritise the comments most likely to need a human read first.
Yes. SleekView checks the moderate_comments capability and any wpDiscuz role caps before each drag. Roles without permission see the board in read-only mode, while editors and moderators can drag cards freely, which mirrors the way the WordPress admin already gates comment actions.
Yes. Each board takes a post ID, category ID, or set of IDs as a filter, so a section editor only sees comments under their section. This is useful for niche review sites, course blogs, or community sites where different teams own different sections and triage on their own pace.
Yes. The like count and rating value live in wpDiscuz meta and can be added to the card front. This makes it easy to spot helpful comments that deserve to be pinned and to find any rating votes that look manipulated, both of which are useful for a healthy comment section.
No. Trash is a soft state managed by WordPress, and dragging into Trash calls wp_trash_comment, which moves the comment to trash without deleting it. A reverse drag back to Pending or Approved restores the comment with its history, just like the WordPress admin does.
Yes. Card meta can include the time since the comment was posted, and the Pending column can sort by that field so the oldest comments rise to the top. This makes the team's daily target concrete and makes long waits obvious to any moderator who opens the board first.
Yes. SleekView pages each column, uses indexed queries on comment_approved, and only loads card fields for visible columns. Large blogs stay responsive because the heavy comment body is only fetched for the cards currently on screen at any time.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout