SleekView Kanban for Stachethemes Event Calendar
Stachethemes stores each entry as a sec_event post with a normal post_status, plus event meta for start and end dates and a recurring rule. SleekView Kanban reads those rows, groups them by post_status, and shows one card per event with the date and venue on the front.
♾️ Lifetime License available
Stop scrolling the event list for whatever is still in draft
Stachethemes Event Calendar saves every event as a custom post type, usually sec_event, with the standard WordPress post_status field on each row. The All Events screen is a long admin list with filter pills for status and category and a paged table of titles, dates, and authors. Events drift between draft, scheduled, and published as editors finish copy, pick covers, and confirm dates with venues. The list view shows them all mixed together.
SleekView reads the same sec_event rows from wp_posts and joins event meta for _sec_event_start, _sec_event_end, and the venue or location key your install uses. Flip the view to Kanban and pick post_status as the group column. SleekView builds one column per status, draft, future, publish, and private, and one card per event with the title, the start date, and the venue on the front.
Drag a card from Draft into Future and SleekView writes the new post_status back to wp_posts, then triggers the standard WordPress save_post hooks so any Stachethemes side effects fire normally. Recurring events keep their parent rule and only the parent row moves between columns. Trashed events stay out of the board unless you add Trash as a fifth column on purpose.
Workflow
From sec_event posts to a kanban board in four steps
Connect SleekView to Stachethemes
Pick post_status as the group column
Choose what shows on each card
Enable drag and drop writeback
Sample board
Sample Stachethemes events board
Comparison
Default Stachethemes list vs SleekView Kanban
Default Stachethemes events
- All Events stays a paginated list with status filter pills and no board mode
- Bulk edit changes status but you still scroll back into the list to see the result
- Recurring events and one-off events sit in the same table with no visual separation
- Venue and start date are buried in the row, not visible at a glance
- No drag and drop between draft, scheduled, and published in a single screen
SleekView Kanban
-
Group sec_event rows by
post_statuswith one column per stage in your data -
Card fronts show title, start date from
_sec_event_start, and venue meta -
Drag and drop writes back through
wp_update_postand fires save_post hooks - Recurring rule rows stay grouped under the parent event, not duplicated per occurrence
- Capability checks match the All Events screen so editor and contributor roles behave the same
Features
What SleekView Kanban gives you for Stachethemes Event Calendar
Real event meta on the card front
Start date, end date, venue, and author from the sec_event meta keys render on the card front so the board reads as a working schedule and not a generic todo list.
Drag and drop writeback
Moving an event from Draft to Future updates post_status through wp_update_post and fires the same save_post hooks Stachethemes already relies on for cache and feed refreshes.
Role-scoped boards for editors
Save a board per role so contributors only see their own drafts, editors see the full pipeline, and authors keep the WordPress capability map intact across drag actions.
Audience
Who runs a Stachethemes events board with SleekView
Editorial teams
Move events from Draft through Scheduled to Published as copy lands and dates are confirmed without scrolling the All Events list.
Marketing managers
Watch the Scheduled column to see what is queued for the next four weeks and what still sits in Draft waiting on assets.
Site owners
Keep a Private column for board and investor events so they never accidentally leak into the public Stachethemes calendar.
The bigger picture
Event calendars are pipelines, the list view hides that
A Stachethemes calendar is rarely a flat list of published events. There is always a column of drafts waiting on copy, a column of scheduled events ready to go live, and a small column of private events for internal use. The default All Events screen flattens those stages into rows with a status filter you have to click into.
SleekView reads the same sec_event rows and turns post_status into real columns, so the same data becomes a visible pipeline. Editors see what is stuck in Draft. Marketing sees what is queued for the month.
Site owners keep private events visibly separate. Dragging an event between columns updates post_status the same way Quick Edit does, hits the same capability checks, and fires save_post so any Stachethemes side effects stay intact. The board does not replace the calendar, it adds the missing pipeline view on top of the same data.
Questions
Common questions about SleekView Kanban for Stachethemes Event Calendar
Yes. Recurring events are stored as a single sec_event parent row with a recurring rule in meta. SleekView reads the parent row, so the board shows one card per series, not one card per occurrence. Moving the parent updates post_status for the whole series the same way Stachethemes does.
Yes. SleekView writes the new value through wp_update_post and lets the standard save_post hooks fire. Any Stachethemes cache refresh, feed regeneration, or notification that already runs on save_post keeps running normally on a drag.
Yes. Drag actions check the same capabilities the All Events screen uses, so a contributor cannot move someone else's event into Published, and an editor sees the full pipeline. Boards can also be scoped per role so each user only sees what they should.
SleekView builds columns from the distinct post_status values it finds on your sec_event rows, so any custom status registered through register_post_status shows up as a column automatically. You can also pin or hide columns in the board config.
Yes. post_status is the default for an editorial pipeline, but any column on sec_event or any joined meta key can be the group column. Venue, location, taxonomy terms, and the author ID all work.
Yes. The frontend calendar still renders from the same sec_event rows. SleekView Kanban is an admin reading and editing layer on the same data, so frontend output and the board always reflect the same database state.
Yes. Any saved kanban view can be embedded on a frontend page through the SleekView shortcode with role-based access, so an event manager can review the pipeline without logging into wp-admin.
Only if your Stachethemes setup or another plugin has already hooked save_post or transition_post_status to send notifications. SleekView fires the standard hooks, so existing notification logic runs the same way as a manual status change in Quick Edit.
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