No. SleekView Feedback reads directly from whatever table or post type Blog Merger is using, including network option rows and any custom log table at the network level. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders.

Yes. SleekView ships with anonymous voting backed by cookies, so public visitors can upvote merges without an account. You can also require subsite login if you want the board restricted to editors or staff, and the same view handles both modes with a single toggle.

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep network boards honest without forcing a signup wall in front of subsite editors.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one source blog ID, one target blog ID, one merge status, or any combination of fields Blog Merger already stores. Different boards on different pages can use different filters.

The Conflict category is just a value on the row. You can write it into a network option key Blog Merger already understands or a dedicated column. Either way it shows up in network admin alongside the failing merge, so the super admin can see the flag without leaving WordPress.

They write back to the source column, which means Blog Merger and any of your own queries can sort future merges, retries, and consolidation lists by that score. Several networks use the score to gate which recipes get patched first, making the board operational not vanity reporting.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any template without touching the page editor.

The view paginates server side and only loads the rows it needs to render the current page. Indexed columns stay fast even on long tables. For really big networks, scoping the board by source or target blog keeps both the query and the audience focused, so the page feels snappy at scale.