✨ 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 All-in-One Event Calendar: events as tables

All-in-One Event Calendar models events as a custom post type with iCalendar-friendly meta. SleekView turns that store into the planning surface the front-end calendar was never meant to be.

♾️ Lifetime License available

SleekView table view for All-in-One Event Calendar

Every event laid out for planning, not browsing

All-in-One Event Calendar (ai1ec) stores events as the ai1ec_event post type with iCalendar-aligned meta — start and end timestamps, venue and address fields, category, recurrence rule, and contact details. The plugin shines on the front end with month, week, agenda, and posterboard views; the admin side is a standard WordPress posts list, which is the wrong shape for the planning rituals organizers actually run.

SleekView reads the ai1ec event CPT and promotes the iCalendar meta to first-class columns. Start, end, venue, address, category, contact, and recurrence rule sit alongside title and status. Inline edits write back to the same meta keys ai1ec uses for the front-end calendar, which means a rescheduled event updates the public month view without an editor round trip. Recurring events surface as parent rows with child instances available through a filter or expansion.

For organizers the unlock is the planning surface: a saved view for upcoming events with a two-week horizon, a filter by venue to spot a double booking, a category grouping for the marketing team's newsletter pull. The front-end calendar continues to read the same meta, so changes made in the grid render on the site immediately.

Workflow

From an iCalendar store to a planning grid

1

Connect to ai1ec_event

Create a SleekView against the ai1ec event CPT. Title, status, and date are detected automatically, alongside the iCalendar-aligned meta keys for start, end, venue, address, category, and recurrence.
2

Promote planning columns

Add start, end, venue, category, and contact to the column set. Save a default view that mirrors the planning meeting: title, start, venue, category, status, sorted by start date.
3

Pin organizer views

Save filters like Upcoming, Cancelled this month, By venue, and By category. Each view captures filters, columns, and sort, so the rituals reopen with a click.
4

Edit and export

Reschedule, cancel, or move venues inline. Bulk update during weather or venue changes. Export filtered category views as CSV for newsletters and social campaigns.

Sample columns

A typical ai1ec events view

Upcoming events grouped by week with venue, category, and status side by side.
Source: WordPress posts/postmeta
Event Start Venue Category Recurring Status
Founder Coffee 2026-05-08 09:00 The Hub Networking Weekly Published
Product Launch 2026-05-14 18:00 Studio Loft Launch No Draft
Open Mic 2026-05-22 20:00 Cafe Nord Music Monthly Published
Workshop Postponed 2026-04-29 10:00 Studio B Workshop No Cancelled

Comparison

Default ai1ec admin vs SleekView

Default ai1ec admin

  • Event list reuses the WordPress posts table with limited columns
  • iCalendar meta hidden behind the event editor
  • Cannot edit start time or venue from the list
  • No saved views for upcoming, recurring, or by venue
  • Recurring events feel detached from their parent in the admin

SleekView

  • Promote start, end, venue, and category to sortable columns
  • Edit event time and status inline; the front-end calendar updates immediately
  • Saved views like Upcoming, Cancelled this month, By venue
  • Group recurring instances under their parent rule
  • Bulk reschedule during venue or weather changes

Features

What SleekView gives you for All-in-One Event Calendar

Plan two weeks at a glance

Sort by start date and scope to the next fourteen days. The saved Upcoming view becomes the screen the team scans before each weekly planning meeting, instead of scrolling the front-end month calendar.

Catch venue conflicts

Group by venue and date to spot double bookings before they reach a customer. Pair with a category filter to see whether the conflict is two networking events or networking versus a workshop.

Reschedule inline

Edit start times, venues, and statuses directly from the grid. Inline edits write through the same ai1ec meta the front-end calendar reads, so the public site reflects the change on the next page load.

Audience

Who uses SleekView for All-in-One Event Calendar

Event organizers

Plan, reschedule, and cancel events from a single grid. Saved views per category and per venue replace the browser-tab juggling between the admin list and the public calendar that organizers fall back on otherwise.

Venue coordinators

Watch venue load across the next month from a single screen. Group by venue, add a date filter, and surface only events with capacity or contact data filled in for the staffing conversation.

Marketing teams

Pull category-scoped event lists for newsletters and social. A saved view per category exports to CSV so the email tool gets the exact set of upcoming events without a curation pass.

The bigger picture

Why an iCalendar plugin needs a planning surface

All-in-One Event Calendar's strength is its alignment with iCalendar: clean data, structured meta, and a front end that renders the result in every view a public visitor expects. The structure makes the data portable; it does not make planning easy. Organizers do not browse a calendar to plan a calendar.

They want a grid that answers questions: what is on next week, where are we booking The Hub twice, which networking events still need a category, which workshops were cancelled but never marked. Those questions are operational and they live one query removed from the way ai1ec presents events in the admin. The data is right there in postmeta, but the WordPress posts list is the wrong shape to surface it.

Treating events as a grid that promotes the iCalendar meta to columns turns the admin from a content editor into the planning surface ai1ec does not try to be. Saved views become the rhythm of the role, inline edits cut the time on a reschedule from minutes to seconds, and the front-end calendar continues to render the same data because every write goes through the same meta keys it already reads.

Questions

Common questions about SleekView for All-in-One Event Calendar

Yes. The recurrence rule is exposed as a column, and recurring instances are visible through filters or expansion. The plugin's recurrence engine continues to drive front-end display because SleekView only reads and writes through the existing meta keys.

 

Yes. Start and end timestamps are editable cells. Edits write to the same meta keys ai1ec uses, so the month, week, and agenda views on the front end pick up the new time on the next render.

 

Yes. Venue name, address, and contact fields stored on the event post are detected and can be promoted to columns. Filtering or sorting by venue works as a first-class operation rather than a workaround.

 

Yes. SleekView changes only the admin grid, so the iCalendar feed continues to publish from the same event meta. Imports from external calendars also continue to land in the events CPT and appear in the grid alongside manually created events.

 

Yes. Any post meta on ai1ec_event — registered by the plugin, by ACF, or by Meta Box — can be promoted to a column. Once promoted, the field becomes filterable and exports to CSV like any native field.

 

Yes. SleekView is an admin companion. The front-end month, week, agenda, and posterboard views continue to render normally because every change writes through the same ai1ec meta the public templates already read.

 

Yes. Bulk reschedule, bulk status change, and bulk category assignment all work across selected rows. Bulk operations are particularly useful when a venue cancels and a batch of events needs to move to a new location.

 

Activity has been intermittent over the years, which is exactly why a thin admin layer that reads and writes the same meta keys is useful. SleekView depends only on the events CPT and its meta, not on plugin internals, so it keeps working as long as ai1ec keeps storing data the way it always has.

 

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