SleekView for Timely: events and registrations as tables
Timely (the maintained continuation of the All-in-One Event Calendar codebase) stores events with iCalendar-aligned meta. SleekView reads that structure into the planning grid organizers actually need.
♾️ Lifetime License available
Timely events with the planning surface organizers need
Timely is the maintained continuation of the All-in-One Event Calendar codebase, with a hosted SaaS option and a self-hosted WordPress plugin that stores events in the familiar CPT-plus-meta shape: start and end timestamps, venue and address fields, category, recurrence rule, and contact information. The front end ships rich calendar views; the admin side is the standard WordPress posts list, which is the wrong shape for the planning rhythms event teams actually run.
SleekView reads the Timely events CPT and promotes the iCalendar meta to first-class columns. Start, end, venue, address, category, and recurrence rule sit alongside title and status. Inline edits write to the same meta keys Timely uses, so the front-end calendar reflects rescheduled times on the next page load. Recurring events surface as parent rows with child instances available through a filter or expansion.
For organizers the difference is concrete: instead of scrolling the front-end month view to plan the next two weeks, they open a saved Upcoming view filtered by date and grouped by category. Venue conflicts surface from a venue filter rather than a memory check. Category-scoped exports replace hand curation for the weekly newsletter.
Workflow
From a posts list to a Timely planning grid
Connect to Timely events
Promote planning columns
Pin organizer views
Edit and export
Sample columns
A typical Timely events view
WordPress posts/postmeta
| Event | Start | Venue | Category | Recurrence | Status |
|---|---|---|---|---|---|
| City Tour | 2026-05-09 10:00 | Visitor Centre | Tourism | Weekly | Published |
| Author Reading | 2026-05-15 19:00 | Library Hall | Culture | No | Draft |
| Farmers Market | 2026-05-23 08:00 | Town Square | Community | Weekly | Published |
| Cancelled Tour | 2026-05-02 11:00 | Heritage Site | Tourism | No | Cancelled |
Comparison
Default Timely admin vs SleekView
Default Timely 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
- Category and venue filters live in separate UI panels
SleekView
- Promote start, end, venue, and category to sortable columns
- Inline edits to event time, venue, and status
- Saved views like Upcoming, Cancelled this month, By venue
- Group recurring instances under their parent rule
- Bulk reschedule across a series when a venue cancels
Features
What SleekView gives you for Timely
See the planning horizon
Sort by start date with a two-week filter to surface what needs promotion, staffing, or a final venue confirmation. The saved Upcoming view becomes the screen the team scans before each weekly meeting.
Spot venue conflicts
Group by venue and date to catch double bookings before they become customer calls. A saved per-venue view replaces the page-by-page browsing of the front-end calendar.
Reschedule inline
Edit start times, venues, and statuses directly in the grid. Inline edits write through the same Timely meta the front-end calendar reads, so the public site reflects changes on the next render.
Audience
Who uses SleekView for Timely
Event organizers
Plan, reschedule, and cancel events from one grid. Saved views per category and per venue replace the constant switch between the admin list and the front-end 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 call.
Marketing teams
Pull category-scoped event lists for newsletters and social. A saved view per category exports to CSV ready for the email tool, with no per-event hand-curation.
The bigger picture
Why an iCalendar-clean plugin still needs a grid
Timely's lineage runs through one of the cleanest event-data implementations on WordPress: an events CPT with iCalendar-aligned meta, a recurrence engine that maps to RFC 5545, and front-end views that render the result for visitors. The cleanliness is what makes the data portable between hosted and self-hosted setups, but it is not what makes the day-to-day work easier. Organizers do not browse a calendar to plan a calendar.
They want a grid that answers questions: what is on next week, where is the Town Square booked twice, which culture events still need a category, which tours were cancelled but never marked. Those questions are operational, and they live one query removed from the way Timely presents events in the admin. Treating events as a grid that promotes the iCalendar meta to columns finishes the workflow without touching the plugin.
Saved views become the rhythm of the role; inline edits cut the time on a reschedule from minutes to seconds; 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 Timely
Timely offers both a hosted SaaS calendar and a self-hosted WordPress plugin. SleekView works against the self-hosted plugin because that is where the events live as a WordPress CPT in your own database. The hosted product is rendered through embeds and is not part of the WordPress admin we extend.
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 Timely uses, so the front-end calendar views 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 registered against the events CPT — by Timely, by ACF, or by Meta Box — can be promoted to a column. Once promoted, the field becomes filterable and exports cleanly to CSV.
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.
Yes. SleekView is an admin companion. The front-end month, week, and agenda views continue to render normally because every change writes through the same meta keys the public templates already read.
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