✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Event Organiser Pro: events, occurrences & bookings as tables

Event Organiser Pro stores events as the event post type with each occurrence as a row in wp_eo_events, plus bookings written by the Pro add-on. SleekView joins those records into a single admin grid that respects recurrence.

♾️ Lifetime License available

SleekView table view for Event Organiser Pro

Recurring events as a real grid

Event Organiser models recurrence well: a parent event post owns a recurrence pattern, and each occurrence lives as a row in the wp_eo_events table with its own start, end, and event ID reference. Venues sit in the event-venue taxonomy. The Pro add-on layers bookings as eo_booking records with attendee meta and ticket information.

SleekView reads event and joins each occurrence from wp_eo_events as its own filterable row. Door staff filter by occurrence date instead of by parent event, which is the right shape when one parent event runs across twelve weekly dates. Bookings join back to the occurrence through the booking meta, so capacity, attendance, and revenue surface per occurrence.

Inline edits write to the wp_eo_events table directly for occurrence-level changes (date shifts, status flips) and through the plugin's own methods for parent-event changes. Conflict detection prevents two admins from clobbering the same occurrence simultaneously. The result is a planning grid built for recurring schedules, not a flattened event list that pretends every parent is a single date.

Workflow

From parent events to a per-occurrence grid

1

Pick the occurrences source

Create a SleekView against the wp_eo_events table. Date, status, and parent event ID are detected automatically and ready to drive the grid.
2

Join parent events and venues

Use the parent post ID to join in event title and recurrence pattern, and the event-venue taxonomy to surface venue context on every row.
3

Pin recurrence-aware views

Save Next 14 days, By venue, Cancelled last 30 days, and By parent event. Each saved view holds filters, columns, and sort so the recurring-schedule workflow reopens with one click.
4

Edit and bulk-update

Cancel a single occurrence, reschedule a date, or bulk-update an entire week when a venue changes. Writes go through the plugin's columns so the public calendar stays accurate.

Sample columns

A typical Event Organiser Pro occurrences view

Each wp_eo_events occurrence as its own row, with parent event, venue, and bookings count joined inline.
Source: wp_posts (post_type=event, eo_booking) + wp_postmeta + wp_eo_events (occurrences)
Occurrence Parent Event Date Venue Bookings Status
Yoga Class #14 Weekly Yoga May 21 Studio B 18 / 20 Published
Yoga Class #15 Weekly Yoga May 28 Studio B 12 / 20 Pending
Choir Practice #7 Choir Rehearsal Jun 03 Hall A 30 / 30 Published
Cancelled Class Weekly Pilates Apr 28 Studio C 0 / 15 Cancelled

Comparison

Default Event Organiser Pro admin vs SleekView

Default Event Organiser Pro admin

  • Event list shows parent posts only, with no per-occurrence grid
  • Per-occurrence cancellations buried in the recurrence editor
  • Cannot toggle occurrence status or date from a cross-event view
  • Bookings from the Pro add-on live in a separate per-event screen
  • No saved views for upcoming occurrences or by venue

SleekView

  • Show wp_eo_events rows as the primary grid, not just parent events
  • Join parent event title, venue taxonomy, and booking count onto each occurrence
  • Inline edit occurrence date, status, and notes
  • Save views like Upcoming next 14 days or By venue per role
  • Bulk-cancel occurrences when a venue or staff change forces a schedule shift

Features

What SleekView gives you for Event Organiser Pro

Occurrence-level grid

Treat each wp_eo_events row as a real entity. Filter by occurrence date for the next 14 days rather than scrolling parent events that own twelve dates each.

Recurrence-aware joins

Join parent event title, venue taxonomy, and capacity onto every occurrence. The Weekly Yoga parent stays clean while the occurrence grid drives the planning.

Inline reschedule

Edit occurrence date or cancel a single instance from the grid. Writes go to wp_eo_events directly, leaving the parent event's recurrence pattern intact.

Audience

Who uses SleekView for Event Organiser Pro

Class and series operators

Weekly yoga, choir, and language schools live on per-occurrence operations. Saved views per parent event surface attendance, cancellations, and venue conflicts for the next month at a glance.

Venue managers

Filter occurrences by venue taxonomy term to balance bookings. The By venue view flags double-bookings at event-venue records before they reach customer support.

Booking leads

When the Pro bookings add-on is active, join eo_booking records to occurrences. Capacity-at-risk and Pending-payment views per occurrence replace per-event scrolling.

The bigger picture

Why recurring schedules need an occurrence-level grid

Event Organiser Pro's value lives in its recurrence engine. A yoga studio, a choir, a language school, a community theater group: each runs on weekly or monthly patterns that the plugin captures cleanly through a parent event and the wp_eo_events occurrence table. The admin lists parent events, which is the right shape for editorial work and the wrong shape for operations.

A studio manager planning next week is not thinking about the parent event Weekly Yoga; they are thinking about the twelve concrete occurrences that need confirmation, the one cancellation, the venue swap on Thursday. Treating wp_eo_events as a real grid surfaces the operational view that the parent-event list cannot. Saved views become the rituals of each role, inline edits route through the same table the plugin reads internally, and a per-occurrence cancellation no longer means hunting through a recurrence editor.

The data was always there; the grid finally matches the work.

Questions

Common questions about SleekView for Event Organiser Pro

Yes. The plugin stores each occurrence as a row in wp_eo_events with a foreign key to the parent event post. SleekView treats those rows as the primary entity, which matches how class-and-series operators think about their week.

 

Yes. Per-occurrence status writes to wp_eo_events directly, leaving the parent event's recurrence pattern intact. The plugin's existing cancellation logic still applies because SleekView writes to the same columns.

 

Yes. When the bookings add-on is active, eo_booking records form a second source that joins back to occurrences through the booking meta. Capacity and payment status surface as columns on the occurrence row.

 

Yes. The event-venue taxonomy joins as a real column, including venue meta where Event Organiser exposes it. Filter and group by venue without leaving the grid.

 

Queries against wp_eo_events are date-indexed, so a 5-year weekly recurrence still paginates fast as long as the active view filters by a date range. The recommended pattern is one saved view per role with a relative date filter like Next 30 days.

 

Yes. The grid spans parent events, so a single bulk action can cancel or reschedule occurrences across multiple parents (for example, all classes at Studio B next week).

 

Yes. Event Organiser's front-end calendar reads from the same wp_eo_events table and parent meta. SleekView writes through the same columns, so the public calendar reflects changes immediately.

 

Yes. The plugin's ICS feed reads from the same occurrence table, so changes made in the grid flow into the feed without extra configuration. Subscribers see the same schedule the admin sees.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView