No. SleekView Feedback reads directly from the ajde_events post type and meta that EventON Pro already maintains. You pick the columns for votes, status, category, author, and title, and the board renders. There is no extra sync job, no duplicate data, and EventON keeps managing the calendar untouched.

Yes. SleekView ships anonymous voting backed by cookies so any visitor can upvote EventON events without an account. You can also require login if you want the board restricted to past attendees or paid members, and the same view handles both modes through a single setting.

Each visitor gets a cookie scoped vote token per item, and logged in users are tracked by WordPress user ID. The plugin exposes a per IP rate limit so a single household cannot spam the board, which keeps the score honest without forcing a signup wall in front of every attendee.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can filter by start date, location taxonomy, or any EventON meta. A second board on another page can present past events as a public archive while the calendar page only lists upcoming dates.

Bug, Idea, and Request are category values stored on the row. They appear in the WordPress admin next to the EventON event, so the same person editing the calendar can resolve them without bouncing between plugins or losing track of which fix shipped when.

They write back to a meta key on the source event. Your own queries and EventON shortcodes can sort calendar tiles, featured slots, and category archives by that score, which means the board ends up driving what shows on the calendar instead of being a vanity metric.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any calendar 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 meta keys stay fast even on long tables. For very busy organisers, scoping the board by upcoming dates or location keeps the query tight and the audience focused, so the page stays snappy at scale.