Yes. SleekView reads the Simple:Press tables directly, so the connector works on both the core Simple:Press plugin and its add-on packs. The likes column is optional, so sites without sfreputation can still sort by reply count or by a custom meta field updated by another plugin or theme function.

They do. SleekView writes a vote into the Simple:Press likes table, which is the same row Simple:Press itself reads when it builds digests and the inline reaction counter. A tap on the SleekView board shows up in the native forum view immediately and feeds into the next subforum digest email.

Yes. The data source picker lets you filter the underlying query by forum id, parent id, or any topic prefix. A bug reports subforum, a private members-only category, or a single public discussion forum can each get its own dedicated SleekView board on a separate WordPress page without query rewrites.

Status pill updates set the Simple:Press topic prefix you mapped to the status column. That is the only write. The original topic, post body, like totals, and reply count stay untouched, so moderators can revert a status by editing the prefix and any audit log plugin watching prefixes sees the change.

Hidden and deleted topics drop off the board automatically because SleekView queries only visible topics by default. If you want a moderator view that includes hidden items, the query filter accepts a status array, so admins can see Pending or Trash rows without exposing them to logged-out visitors.

No. SleekView paginates the query, caches the sorted set, and only loads the rows needed for the current page. A board with twenty thousand Simple:Press topics serves in roughly the same time as a board with five hundred because the database sort happens once and the cache covers every subsequent visitor.

Anonymous voting is off by default because the Simple:Press likes table 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, useful for public roadmap pages that get traffic from non-members and search engines.

The SleekView config travels with the source mapping. Repoint the data source picker at the new tables (bbPress, BuddyBoss, or any forum schema you can query) and the board renders again. Existing vote data stays in the Simple:Press tables until you drop them, so a rollback is always possible during migration windows.