No. SleekView Feedback reads directly from the event post type, the venue taxonomy, and the bookings table that Event Organiser Pro already maintains. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. Nothing is duplicated, nothing has to sync.

Yes. SleekView ships with anonymous voting backed by cookies so any visitor can upvote events without an account. You can also require login if you want the board restricted to past ticket holders or paying members, and the same view handles both modes with a toggle.

Each visitor gets a cookie scoped vote token per item, and logged in users are tracked by user ID. The plugin exposes a rate limit per IP so a single household cannot spam the board, which is enough to keep the score honest without forcing every attendee to create an account first.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can filter by start date, venue, category, or any meta key Event Organiser Pro already writes. A second board on a different page can show past events as a public archive while the homepage board only lists upcoming dates.

Bug, Idea, and Request are just category values on the row. They show up in the WordPress admin alongside the source event, so the same person managing tickets can see and resolve them without leaving Event Organiser Pro. You can also expose them as a CSV export for a separate support workflow if you prefer.

They write back to the source column, which means your own queries, the event list block, and any custom report can sort future scheduling and recurring runs by that score. Several venues use the score to gate which series get extra dates, which makes the board operational and not just decorative.

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 event archive or single 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 very busy venues, scoping the board by upcoming dates or active series keeps both the query and the audience focused, so the page feels snappy even at scale.