SleekView Feedback for Co-Commenter
SleekView Feedback reads Co-Commenter threads, the reactions table, and per-comment meta, ranks every conversation by reader engagement, and renders an upvote board so the highest-signal threads stop sinking under chronological comment lists that nobody scrolls all the way through.
♾️ Lifetime License available
Why Co-Commenter sites need an upvote view
Co-Commenter extends the default WordPress wp_comments table with threading metadata and writes reactions into a dedicated wp_cocommenter_reactions table. Threads on a busy post can stretch into hundreds of replies, and the default render is chronological inside each branch, so an insightful comment with twenty upvotes might sit twelve scrolls below a short reply posted an hour ago.
SleekView Feedback reuses those exact structures. Pick a numeric column for vote weight (the Co-Commenter reaction total, the reply count under each parent thread, or a custom _score meta), then a status column from comment meta, then a category column from the parent post category. The result is one board sorted by reader engagement instead of by comment timestamp.
Clicking Upvote on a card writes a reaction back to wp_cocommenter_reactions, which means the same signal feeds the inline thread view, the per-comment reaction counter, and any digest plugin already reading Co-Commenter signals. Status pill changes update the comment meta, so moderators close out work from one board without scanning every thread by hand.
Workflow
From Co-Commenter threads to a feedback board
Connect to the Co-Commenter tables
Pick the upvote column
Map status and category
Embed the board on a public page
Sample board
Sample Co-Commenter feedback board
Comparison
Co-Commenter default render versus SleekView Feedback
Default Co-Commenter view
- Threaded view is chronological per branch, so highly-reacted comments sink under newer replies.
- Reaction counts are visible but cannot drive a sort order on a cross-post listing layout out of the box.
- Status meta on a comment is hidden from readers, so admins cannot show a public moderation surface.
- Cross-post discovery does not exist, so finding the most-reacted thread across the site needs manual queries.
- No public board view, so readers cannot see which threads have been promoted to the editorial roadmap.
SleekView Feedback
- Sorts every Co-Commenter thread by your chosen numeric column with one config click in the picker.
- Status pills update Co-Commenter comment meta so existing moderation routines stay intact.
-
Reads
wp_cocommenter_reactionsdirectly, no parallel vote table or shim required. - Category pills reuse the parent post category taxonomy and pick up new categories automatically.
- Upvotes write back to Co-Commenter so reactions still count in the inline thread view downstream.
Features
What SleekView Feedback gives you for Co-Commenter
Native Co-Commenter reactions as votes
SleekView Feedback reads the same reaction rows Co-Commenter already records whenever a reader taps the heart or thumbs-up on a comment. No second vote system to teach the audience, no duplicate counts to reconcile, and every reaction collected since launch becomes the sort order for the public board from the first render.
Parent-post category pills
The category column maps straight to the parent post category taxonomy, so a comment under a Tutorials post lands under a Tutorials pill on the board. Admins do not keep a parallel taxonomy in sync, and new categories appear as new pills automatically the next time the board renders for visitors.
Public status roadmap
Status pills like Planned, In progress, and Shipped come from a Co-Commenter comment meta key you choose. Editing the meta updates the pill on the board, so the editorial team can promote highly-reacted threads to the roadmap without bolting on a separate tool to manage that surface.
Audience
Where Co-Commenter sites use the board
Top discussions page
Embed the board on a Most Active Discussions page so readers see which threads the community has rallied behind. The list reorders itself as reactions accumulate, so the page reflects real reader signal instead of the chronological order Co-Commenter renders inside each post by default.
Editorial story prompts
Editorial teams scan the board for highly-reacted threads as story prompts. A pill column marks each thread Scheduled, In progress, or Published, so writers see exactly which reader conversations have been turned into articles without spelunking through chronological comment lists by hand each morning.
Internal moderator triage
Set the board to admin-only and filter by parent post category to triage incoming threads by team. Moderators move cards from New to Investigating as they pick work up, and every comment meta edit feeds the existing audit trail without bolting on extra logging or workflow tools.
The bigger picture
Why a feedback view beats the Co-Commenter default render
Threaded comment plugins capture incredible signal, but most of it never reaches the surface because every render decision optimizes for one post at a time. A reader writes a thoughtful comment with twenty reactions on a popular article and a week later it sits buried twelve scrolls down inside that single thread, invisible to everyone reading other posts on the site. Editorial teams scroll through tabs trying to find the conversations worth promoting, moderators triage comment by comment, and readers eventually stop investing in longform replies because none of them ever surface beyond the thread where they were posted.
SleekView Feedback flattens the data. It reads the same reactions Co-Commenter already tracks, then surfaces the highest-reacted threads across every post on the site at the top of a clean upvote board. Editorial teams see story prompts ordered by reader signal.
Moderators triage from one ordered list instead of jumping between posts. Readers see their best comments being recognized because the board displays them prominently regardless of which post they were attached to, which is enough to keep longform replies coming.
Questions
Common questions about SleekView Feedback for Co-Commenter
Yes. SleekView reads the Co-Commenter tables and comment meta directly, so it works whether the site runs the free Co-Commenter plugin or paid add-ons like the reactions and moderation upgrades. The reactions schema is identical across tiers, so the connector behaves the same regardless of which features are licensed.
They do. Co-Commenter stores every reaction with the WordPress user ID of the reader who tapped it, and SleekView reads the same rows. Reactions from logged-in users count immediately, and the board can also include guest reactions if Co-Commenter has anonymous voting enabled on the site for unauthenticated readers.
Yes. The data source picker accepts a tax_query for parent post categories and a comment_meta query for the Co-Commenter status meta, so a Tutorials category, a Bug Reports tag, or comments carrying a specific moderation status can each get their own SleekView board on separate WordPress pages.
Status pill updates set the Co-Commenter comment meta key you mapped to the status column. That is the only write. The comment body, reaction totals, and reply chain stay untouched, so moderators can revert a status by editing the meta and any audit log plugin watching comment meta sees the change immediately.
Trashed, spam, and pending comments drop off the board automatically because SleekView queries only approved comments by default. If you want a moderator view that includes pending submissions, the comment_status filter accepts an array, so admins can see Pending or Spam rows without exposing them publicly.
No. SleekView paginates the underlying WP_Comment_Query, caches the sorted set, and only loads the rows needed for the current page. A board with fifty thousand Co-Commenter threads serves in roughly the same time as a board with five hundred because the reaction sort runs once and the cache covers every subsequent visit.
Anonymous voting is supported if Co-Commenter has it enabled at the plugin level. SleekView uses the same fallback Co-Commenter uses for guest readers, which writes a session-keyed reaction that converts to a user-keyed reaction on login. Sites that require login for reactions keep that restriction on the SleekView board too.
The SleekView config travels with the source mapping. Repoint the data source picker at the new schema (wpDiscuz, Thrive Comments, or any comment system you can query) and the board renders again. Co-Commenter reaction data stays in its tables until you drop them, so a rollback during a migration window is always possible.
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