SleekView Feedback for Comments Evolved
SleekView Feedback reads the merged Comments Evolved log across Disqus, Facebook, and native WordPress, ranks every thread by reactions, and renders an upvote board so high-signal asks stop drowning under chronological streams that nobody scrolls past the third comment of.
♾️ Lifetime License available
Why Comments Evolved sites need an upvote view
Comments Evolved aggregates threads from Disqus, Facebook, Google+ legacy, and native WordPress into a single tab UI, writing the merged log into wp_comments_evolved_log with the source provider in the provider column. The native tab view is chronological per provider, so a thread with fifty Disqus upvotes is invisible to anyone reading the Facebook tab and vice versa.
SleekView Feedback reuses the merged log. Pick a numeric column for vote weight (the upvote count summed across providers, the reply count per thread, or a custom _score meta), then a status column from a comment meta key, then a category column from the parent post category or the provider column itself. The result is one board sorted by cross-provider engagement on a public page.
Clicking Upvote on a card writes a reaction back to wp_comments_evolved_log against the same provider the comment came from, which means the signal still flows back to Disqus, Facebook, or native WordPress through the existing Comments Evolved providers. Status pill changes update the comment meta, so moderators close out work from one board.
Workflow
From Comments Evolved threads to a feedback board
Connect to the merged log
Pick the upvote column
Map status and category
Embed the board on a public page
Sample board
Sample Comments Evolved feedback board
Comparison
Comments Evolved tabs versus SleekView Feedback
Default Comments Evolved tabs
- Tabs split engagement by provider, so a thread with fifty Disqus upvotes is invisible on the Facebook tab.
- Per-tab views are chronological, so highly-reacted threads sink under newer replies inside each provider.
- Cross-provider total upvotes are computed but never used as a sort order on a unified front-end view.
- Status meta is hidden from readers, so the site cannot expose a public moderation or roadmap surface.
- No public board view, so readers cannot see which threads have been promoted to the editorial roadmap.
SleekView Feedback
-
Sorts every
wp_comments_evolved_logrow by your chosen numeric column with one config click. - Status pills update the Comments Evolved meta key so moderation routines keep working as designed.
- Reads the merged log directly, no parallel vote table or per-provider REST glue to maintain manually.
- Category pills can use the provider column or the parent post category, depending on the board purpose.
- Upvotes write to the merged log against the original provider so signal flows back through the sync.
Features
What SleekView Feedback gives you for Comments Evolved
Cross-provider votes
SleekView Feedback reads the cross-provider upvote total Comments Evolved already aggregates, so a thread with twenty Disqus upvotes and ten Facebook reactions ranks above a single-provider thread with twenty-five upvotes. Editorial teams see real cross-channel signal instead of three separate tabs nobody scrolls all the way through.
Provider-aware pills
The category column can map to the provider column directly, so each card shows a colored pill for Disqus, Facebook, or Native. Readers see at a glance where the conversation is happening, and editorial teams can filter for one provider when triaging without leaving the unified board view.
Public status roadmap
Status pills like Planned, In progress, and Shipped come from a Comments Evolved meta key you choose. Editing the meta updates the pill on the board, so the editorial team can promote highly-reacted threads to a public roadmap without bolting on a separate roadmap tool next to Comments Evolved.
Audience
Where Comments Evolved sites use the board
Cross-provider top discussions
Embed the board on a Most Active Discussions page so readers see threads ranked by cross-provider reactions rather than per-tab chronology. The list reorders itself as new reactions land on any provider, so the page reflects total reader signal across Disqus, Facebook, and native WordPress at once.
Editorial story prompts
Editorial teams scan the board for highly-reacted threads as story prompts regardless of which provider they originated on. A pill column marks each thread Scheduled, In progress, or Published, so writers see exactly which conversations have been turned into articles without scanning three separate tabs.
Internal moderator triage
Set the board to admin-only and filter by parent post category or provider to triage incoming threads by team or by channel. Moderators move cards from New to Investigating as they pick work up, and every meta edit feeds the existing Comments Evolved audit trail without extra tools.
The bigger picture
Why a feedback view beats the Comments Evolved tabs
The whole point of Comments Evolved is to surface conversation from every channel in one widget, but the tabs still separate signal at render time. A reader who only checks the Facebook tab never sees the twenty-upvote Disqus thread, and the editorial team gets a fragmented picture of which conversations actually mattered. The native chronological order inside each tab makes it worse because high-signal threads sink as soon as a new low-effort reply lands.
Moderators end up flipping between tabs, the editorial team writes the roadmap from gut feel, and readers eventually stop replying because their best comments never surface above the fold. SleekView Feedback flattens the data. It reads the merged log Comments Evolved already maintains, then ranks every thread by total cross-provider engagement on one ordered board.
Editorial teams see story prompts ordered by combined signal. Moderators triage from one list instead of three tabs. Readers see their best contributions getting recognition because the board displays them regardless of which provider hosted the original thread, which keeps engagement coming back across every channel.
Questions
Common questions about SleekView Feedback for Comments Evolved
Yes. SleekView reads the merged log Comments Evolved writes, which includes every provider the site has ever enabled including Google+ archives. Active providers like Disqus, Facebook, and native WordPress feed the board in real time, and dormant providers still appear because their historical rows remain in the log.
They do. Comments Evolved polls each providers API and writes the upvote totals back into the merged log. A Disqus upvote from a non-WordPress visitor lands in the log on the next sync, so it counts toward the SleekView sort order even though the voter never visited the WordPress site directly with a logged-in account.
Yes. The data source picker accepts a filter on the Comments Evolved provider column and on the parent post category taxonomy, so a Disqus-only board, a Facebook-only board, or a category-specific board can each get its own SleekView page without writing custom queries on the theme side.
It writes back into the merged log under the original provider. The actual sync to Disqus or Facebook depends on whether Comments Evolved has write permissions for that provider. If write access is enabled, the upvote propagates on the next sync. If not, the vote stays inside Comments Evolved and SleekView together.
Trashed, spam, and pending rows drop off the board automatically because SleekView queries only approved entries by default. If you want a moderator view that includes pending or spam, the status filter accepts an array, so admins can see those rows in an internal board without exposing them to public readers.
No. SleekView paginates the underlying query, caches the sorted set, and only loads the rows needed for the current page. A board with fifty thousand merged rows serves in roughly the same time as a board with five hundred because the cross-provider sort runs once and the cache covers every subsequent visit.
Anonymous voting is off by default because the merged log expects a provider-keyed identity. You can enable a SleekView session-based fallback that stores guest votes in its own table and merges them on login or provider auth, useful for roadmap pages where visitors should still vote without picking a provider.
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. The Comments Evolved log stays in WordPress until you drop it, 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