No. SleekView reads the vb_thread CPT that vBulletin Bridge mirrors locally, and any upvote increment lands on a WordPress postmeta key. Status pill edits update the same postmeta key, which vBulletin Bridge can choose to mirror back into a vBulletin thread prefix during the next sync cycle.

Yes. The Upvote button supports guest votes with a per-IP and per-session lock to keep counts honest. If you would rather restrict votes to logged-in users or specific roles like Editor or Moderator, you can flip that in the view settings without touching any code at all.

You map a vb_review_status meta key on the vb_thread entries when you build the view. SleekView shows a colored pill for each value, and any thread without a status simply renders without a pill rather than blocking the card from showing on the board at all in public.

Yes. SleekView reads whatever vBulletin Bridge has mirrored. Multiple forum ids, hidden subforums, and per-language forums can be filtered into separate saved views, so a marketing page can show one subforum and a support page can show another without conflicting category chips.

Yes. Every saved view has its own role and capability scope, so you can publish a public Community Ops feedback wall on an editorial page and a separate Moderator Triage queue that only Moderators and Admins can see. Both views share the same vBulletin data underneath.

When the underlying vb_thread record is removed by the next sync, SleekView removes the card on the next refresh. If the thread is hidden rather than deleted, the card disappears from the public view but the upvote meta is preserved on the hidden row for export and history.

Yes. SleekView views render as shortcodes, Gutenberg blocks, and short HTML snippets. Most teams drop a Top reactions view above or beside the vBulletin-rendered widget on the same community page so the upvote board and the native chronological view share the page without conflict.

SleekView paginates and sorts at the database level rather than loading every vb_thread into memory, so a sync history with tens of thousands of threads still renders the top of the feedback board in well under a second on a normal shared host with default caching enabled today.