Yes. SleekView reads the wp_comments table and the wpDiscuz commentmeta keys directly, so it works on the free wpDiscuz core install as well as the paid Pro stack. Some vote sources, like the user rating bar and certain reaction add-ons, only exist on Pro, but the board itself renders fine on either tier.

They do. The inline widget writes to wpdiscuz_thread_likes through the standard comment meta API, and SleekView Feedback reads from that exact key. A tap on the inline up arrow shows up on the board on the next render and counts toward the sort order without any extra wiring.

Yes. The data source picker lets you filter the underlying query by post ID, post taxonomy term, parent comment ID, or any commentmeta key wpDiscuz writes. A single article, a category, or a label can each get its own dedicated SleekView board on a separate WordPress page.

Status pill changes update the wpDiscuz comment label meta that you mapped to the status column. That is the only write. The comment content, author, and reaction counts stay untouched, so moderators can revert a status by editing the label, and any audit log plugin watching commentmeta sees the change.

Trashed, spam, and held comments drop off the board automatically because SleekView queries only approved comments by default. If you want a moderator view that includes pending or held items, the query filter accepts a status array, so admins can see them without exposing the rows to readers.

No. SleekView paginates the underlying query, caches the sorted set per page slug, and only fetches the rows it needs for the current page. A board over half a million wpDiscuz comments serves in the same time as one with five hundred because the database does the heavy lifting once and the cache covers every subsequent visitor.

Anonymous voting is off by default because wpdiscuz_thread_likes expects a user ID. You can enable a SleekView session-based fallback that stores guest votes in its own table and merges them on login, which suits public roadmap pages that receive traffic from readers who do not have a wpDiscuz account.

The board keeps rendering as long as wp_comments still exists, since SleekView falls back to the standard WordPress comment columns when wpDiscuz meta is missing. If the comment table itself disappears the board fails closed with a clear empty state instead of a fatal error on the rendered page.