Yes. SleekView reads the standard rtMedia tables and meta layer, so it works on any site running the free rtMedia plugin. Premium rtMedia add-ons are supported but not required, and the typical setup takes about five minutes once SleekView is installed and the media post type is selected as the data source.

Both options are supported. The upvote column accepts the rtMedia like meta directly, or it can read from the shared BuddyPress favorites table for sites that prefer a unified engagement counter across all BuddyPress content types. Choose whichever counter your community is already accustomed to.

Yes. SleekView queries media through the standard rtMedia permission layer, which honors public, private, members-only, and friends-only visibility. A logged-out visitor never sees private uploads on a public board, and album-level visibility rules are enforced exactly as rtMedia would enforce them on the regular gallery.

Yes, if the upvote column is mapped to the rtMedia like meta. Each click writes to the same row the rtMedia like button writes to, so the gallery, the activity stream, and any third-party reporting plugin all show the same number after each click without any reconciliation.

Edited uploads stay on the board with their updated metadata, while the underlying like counter and BuddyPress favorites carry over because the row keeps its ID. If an upload is fully replaced by a new file, the new file inherits the same ID and the existing engagement totals continue to count.

Yes. The data source picker accepts an album term filter or a group ID filter, so an Album board and a Group media board can live on separate pages with separate sort columns and separate status mappings. Each board only queries the rows it is scoped to and respects the underlying privacy rules.

No. SleekView paginates the underlying query, caches the sorted set, and uses indexed columns for the like and favorite joins. A board with hundreds of thousands of rtMedia uploads renders in the same time as a small board because the database does the sort once and the cache covers subsequent visitors.

The board fails closed with a clear empty state because the rtMedia tables are no longer queryable. Reactivating rtMedia restores the data without any SleekView reconfiguration, and no upload metadata is lost during a temporary deactivation because the underlying tables remain in the database.