SleekView Kanban for Simple Calendar Pro
Simple Calendar Pro pulls events from Google and iCalendar feeds and stores them as cached event rows with a source status. SleekView Kanban reads those rows and renders one card per event, grouped by status, drag to hide or restore locally.
♾️ Lifetime License available
Read Simple Calendar synced events as a board
Simple Calendar Pro authenticates against a Google Calendar feed or an iCalendar URL and stores each pulled event as a cached row in simcal_feeds_cache with the source calendar ID, the event title, the start time, and the source status field set to confirmed, tentative, or cancelled. Each feed lives as a gce_feed custom post with the sync schedule and the last sync state stored as meta.
SleekView Kanban reads the cached event rows and groups them by the source status field combined with a local hide flag. The board shows Confirmed, Tentative, Cancelled, and Hidden as separate stacks. Each card carries the event title, the source feed name, the start time, and the organiser email pulled from the source, so the calendar manager sees what they need without opening the feed cache table directly through the database.
Dragging a card writes the local hide flag back to the cache row, since the source feed is the canonical store. Moving a card to Hidden flags it as suppressed on the front-end calendar without changing the Google or iCalendar source, moving back to Confirmed re-enables display, and a Cancelled card auto-fades on the public calendar. The audit log records every drag with user and timestamp for accountability.
Workflow
From simcal_feeds_cache rows to a board
Connect SleekView to the cache
Pick the status field as grouping
Choose what shows on each card
Enable drag to flag locally
Sample board
Sample Simple Calendar synced events board
Comparison
Default cache table vs SleekView Kanban
Default Simple Calendar cache
- Feed cache is a hidden table only visible through the SQL console or a phpMyAdmin browse
- No way to drag a synced event into a Hidden column without editing the calendar shortcode
- Cancelled and tentative events mix into the same display feed on the front-end calendar
- Hiding a single event from the calendar takes a shortcode argument or a custom code filter
- Last sync state lives as a meta key on the feed, not visible next to the event rows
SleekView Kanban
-
Groups
simcal_feeds_cacherows on one board by sourcestatus - Drag flags a row as Hidden locally without touching the Google or iCalendar source
- Card front shows event title, source feed name, start time, and organiser email
- Per-feed boards let one calendar manager scope to a single feed at a time on the install
- Audit log records every drag with user, timestamp, and previous local flag value
Features
What SleekView Kanban gives you for Simple Calendar Pro
Real synced event cards
One card per row in simcal_feeds_cache with the event title, source feed name, start time, and organiser email pulled from the Google or iCalendar source, plus the location field from the synced event row.
Drag to flag locally
Moving a card writes the local hide flag on the cache row without touching the Google or iCalendar source, so the front-end calendar reads the flag immediately and the source feed stays exactly as the organiser left it.
Per-feed saved boards
Scope the board so a marketing calendar feed shows one board for that team and a sales feed shows another, or aggregate every feed across the install for an admin board surfacing every event across calendars.
Audience
Who runs Simple Calendar Pro on a kanban board
Calendar managers cleaning up
Drag a card from Confirmed to Hidden when a synced event should not show on the public calendar, without asking the organiser to change the Google or iCalendar source event.
Communications teams
Watch Tentative events move into Confirmed or Cancelled through the week so the public calendar page reflects what the organiser actually plans to run on the day.
Site admins on cleanup
Filter the board to Cancelled and Hidden to clear stale rows from the front-end calendar in a single pass without editing the calendar shortcode arguments by hand.
The bigger picture
Synced calendar events deserve a board
Simple Calendar Pro keeps a local cache so the WordPress site can render the calendar without hitting Google or the iCalendar source on every page load. The cache holds the source status, the start time, the organiser, and the source feed name, but the default reading surface is a SQL table that site managers usually never touch. Tentative events, cancelled events, and events that should be hidden locally all sit together inside the same cache and surface on the front-end without an obvious way to triage them from inside WordPress.
SleekView Kanban turns that cache into a board with Confirmed, Tentative, Cancelled, and Hidden as columns, a count per column at the top, and a card per event with the title, the source feed, and the organiser email on the front. Drag a card to flag it locally without touching the Google or iCalendar source, and the front-end calendar reads the flag immediately.
Questions
Common questions about SleekView Kanban for Simple Calendar Pro
No. SleekView writes only a local hide flag to the simcal_feeds_cache row, the Google or iCalendar source event stays exactly as the organiser left it. This keeps the WordPress display fully under the calendar manager's control without ever pushing back to the source.
Yes. SleekView reads the status field from each simcal_feeds_cache row and renders one column per distinct value. Confirmed, Tentative, and Cancelled show as the three source-side columns, with the local Hidden column added when the local hide flag is set on the row.
Yes. Dragging a card to Hidden writes the local hide flag on the cache row, and the front-end calendar reads the flag and filters the event out of display. The Google or iCalendar source stays untouched, so the organiser sees no change on their side at any point.
Yes. The board can aggregate simcal_feeds_cache rows across every gce_feed post on the install, or be filtered to a single feed by feed ID for a per-calendar view. The grouping field stays the source status, only the filter changes per saved view for each calendar manager.
Yes. SleekView reads any custom field you added to simcal_feeds_cache through a snippet and lets you choose it for the card front. The value matches what the cache row holds because SleekView reads the same row, not a copy stored somewhere else in the WordPress database.
Yes. Saved kanban views are scoped per role and per capability, so calendar managers can see Confirmed and Tentative only, comms can see Cancelled, and admins see every column including Hidden. The underlying cache data does not change, only what each role reads on the board.
Yes. SleekView reads the live simcal_feeds_cache rows on every load, so the next time a scheduled sync runs and updates the cache the board reflects the new statuses on the next refresh. There is no separate index to rebuild because the board reads the same rows the calendar reads.
No. SleekView paginates inside each column and loads card detail on demand, so a feed with several thousand cached events renders the column counts immediately and streams card content as you scroll. Filters and saved views reduce the working set before render.
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