SleekView for All-in-One Event Calendar Pro: events as tables
All-in-One Event Calendar Pro stores events as the ai1ec_event post type with a companion wp_ai1ec_events table holding timing, location, and recurrence rules. SleekView joins those records into one admin grid with inline edits, saved views, and feed-source filters.
♾️ Lifetime License available
AI1EC events as a real grid
All-in-One Event Calendar Pro is unusual: events live as the ai1ec_event post type and a parallel wp_ai1ec_events table that holds start, end, venue, cost, recurrence_rules, and ICS-feed metadata. The default admin presents a stock post list and the calendar UI, which is fine for editorial work and limited for operations.
SleekView reads ai1ec_event and joins the parallel wp_ai1ec_events row onto every post by ID. Start, end, venue, cost, recurrence rules, and feed source promote to first-class columns. The AI1EC ICS-feed table joins so events imported from external calendars surface as filterable rows alongside locally-authored events.
Inline edits write to wp_ai1ec_events directly for timing and recurrence changes, and through the plugin's CRUD methods for post-level changes. ICS-feed events get a read-only flag because their source of truth is external; SleekView surfaces them but routes any edits back to the feed source instead of overwriting silently. The grid respects AI1EC's architecture instead of pretending the parallel table does not exist.
Workflow
From two AI1EC sources to one grid
Connect to ai1ec_event
ai1ec_event post type. SleekView detects the parallel wp_ai1ec_events row and offers its columns for promotion.
Promote AI1EC timing and feed source
start, end, venue, cost, and ICS-feed source as columns. Join wp_ai1ec_event_instances for recurrence-aware filtering.
Pin community-calendar views
Edit and export
Sample columns
A typical AI1EC Pro events view
wp_ai1ec_events joined inline: start, end, venue, cost, and recurrence rules as columns.
wp_posts (post_type=ai1ec_event) + wp_postmeta + wp_ai1ec_events + wp_ai1ec_event_instances
| Event | Start | End | Venue | Source | Status |
|---|---|---|---|---|---|
| City Festival | May 24 10:00 | May 24 22:00 | Town Square | Local | Published |
| Library Talk | Jun 02 18:00 | Jun 02 19:30 | Library Hall | ICS Feed | Imported |
| Spring Market | Jun 14 09:00 | Jun 14 17:00 | Market Square | Local | Draft |
| Cancelled Class | Apr 22 18:00 | Apr 22 20:00 | Studio C | Local | Cancelled |
Comparison
Default AI1EC Pro admin vs SleekView
Default AI1EC Pro admin
-
Event list shows stock post columns, with
wp_ai1ec_eventsdata hidden -
Cannot edit
startorendtimestamps from the list - ICS-feed events not distinguished from locally-authored events in the admin
- Filtering by venue or recurrence requires opening each event
- No saved views for upcoming or feed-only events
SleekView
-
Join
wp_ai1ec_eventstiming, venue, cost, and recurrence onto every post - Promote ICS-feed source as a filterable column with read-only handling
- Inline edit start/end timestamps, venue, and cost for locally-authored events
- Save views like Upcoming local events, Imported feed events, By venue
-
Filter
wp_ai1ec_event_instancesfor recurrence-aware planning
Features
What SleekView gives you for All-in-One Event Calendar Pro
AI1EC timing as columns
Promote start, end, venue, and cost from wp_ai1ec_events. Sort by start timestamp and filter by venue in the same view without opening events one by one.
Feed source aware
ICS-feed imports are flagged distinctly. Local-only and Imported views separate operations: edit the local events, refresh the feed for imports, route changes back to the source for shared calendars.
Recurrence-aware joins
wp_ai1ec_event_instances joins back so each occurrence appears as a filterable row. Per-occurrence cancellation is one cell edit, not a recurrence-editor walk.
Audience
Who uses SleekView for All-in-One Event Calendar Pro
Community calendar admins
AI1EC's strength is aggregating local and feed events. The Imported view and Local view side-by-side let admins triage feed quality and approve or hide events without opening each post.
Feed integrators
Filter ai1ec_event by ICS source to audit external feeds. Per-source views surface duplicates, low-quality entries, or feeds that have stopped refreshing.
Venue managers
Group events by wp_ai1ec_events.venue to spot conflicts. The By venue view flags double-bookings before they reach customer support.
The bigger picture
Why community calendars need a feed-aware grid
All-in-One Event Calendar Pro carved out a niche around community calendars: a calendar that aggregates locally-authored events with ICS-feed imports from external sources. The architecture reflects that with a parallel wp_ai1ec_events table for timing and recurrence and a separate import pipeline for feeds. The default admin presents both as one undifferentiated post list, which is exactly the wrong shape for the moderation work that community-calendar admins actually do.
An admin running a city events page wants to triage which feeds are still healthy, which local submissions need review, which venues are overbooked next month, and which recurrences need a single-instance tweak. The data is there in ai1ec_event, wp_ai1ec_events, and wp_ai1ec_event_instances; it just needs a grid that joins them and respects the feed source. Treating AI1EC's architecture as a real grid surfaces the moderation views the role demands, and routes edits back to the right place so the local-versus-imported distinction stays clean.
Questions
Common questions about SleekView for All-in-One Event Calendar Pro
Yes. Each ai1ec_event post has a matching row in wp_ai1ec_events keyed by post ID. SleekView joins them automatically so timing, venue, cost, and recurrence rules surface as columns without manual mapping.
Feed-imported events are flagged as such and treated as read-only in the grid because their source of truth is the external feed. SleekView surfaces them for filtering and reporting, and routes any edits back to the feed source rather than overwriting silently.
Yes, for locally-authored events. start and end in wp_ai1ec_events are editable cells. Writes go to the same columns AI1EC reads internally, so the front-end calendar updates immediately.
Yes. wp_ai1ec_event_instances joins back for recurrence-aware planning. Each instance can be filtered, and per-occurrence cancellations or reschedules write to the instance row without breaking the parent recurrence rule.
Yes. Any meta on ai1ec_event can be promoted to a column. Pro-specific fields like contact details and ticket URLs join inline alongside the timing columns from wp_ai1ec_events.
Yes. Any filtered view exports to CSV with the columns you choose. Community calendar admins typically save one Imported view for moderation and one Local view for editorial review.
Queries are pinned to indexed columns like start and end on wp_ai1ec_events. Saved views with a date filter keep the grid responsive at scale because the underlying join is on indexed integer columns.
Yes. SleekView is an admin-side companion. The front-end calendar widget, single-event template, and ICS-feed import keep running because all changes use the same wp_ai1ec_events columns and post type that AI1EC reads.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout