SleekView for PublishPress Future
SleekView reads _expiration_date and _expiration_date_options postmeta and joins each scheduled action with its post, so every PublishPress Future expiration becomes a row in one calendar-style table.
♾️ Lifetime License available
Post expirations are easy to set, hard to audit
PublishPress Future, formerly Post Expirator, schedules actions on individual posts: trash a campaign page on a date, unpublish a webinar, change a category, stick a banner. The plugin handles the cron work cleanly, but the configuration lives entirely in a meta box per post. After a year of editorial work, a marketing team easily ends up with dozens of scheduled expirations spread across the site with no way to see them as a single calendar.
SleekView reads the canonical _expiration_date and _expiration_date_options postmeta keys and joins them with the post, type, author and configured action. Every scheduled expiration becomes a row in a sortable table. Filter to expirations in the next fourteen days and confirm each one is still wanted. Filter to action equals trash and post type equals page to make sure no campaign landing page is going to silently disappear. Sort by expiry to see the next two months as a real timeline.
Inline edits push changes through the same save path PublishPress Future uses, so the cron is rescheduled, any custom expiration actions fire correctly and the Future Action Log records the change. The result is the calendar view that the meta box never gives you.
Workflow
Turn scattered expirations into one timeline
Read expiration meta
See it as a timeline
Triage upcoming risk
Bulk reschedule
Sample columns
Scheduled expirations
wp_postmeta
| Post | Type | Action | Expiry | Author | State |
|---|---|---|---|---|---|
| Spring Promo | Page | Trash | 2026-05-15 | Anna | Soon |
| Old Webinar | Post | Unpublish | 2026-04-26 | Marc | Tomorrow |
| Conference Recap | Post | Change category | 2026-09-10 | Lina | Future |
| Holiday Banner | Page | Stick | 2026-12-20 | Anna | Future |
Comparison
PublishPress Future admin vs SleekView
PublishPress Future admin
- Expirations live in a meta box on each post
- Future Action Logs are read only
- No flat list to sort by date and action
- Bulk reschedule across posts is not exposed
- Filtering by action type is limited
SleekView
- Joins post data and Future expiration metadata in one table
- Filter by action type, post type and expiry date
- Sort by expiry across all expirations together
- Inline edit expiry date and configured action
- Bulk reschedule or cancel expirations across many posts
Features
What SleekView gives you for PublishPress Future
Expiry calendar
Every scheduled action across the site in one sortable table with post, type, action, expiry and author so nothing fires by surprise.
Triage what is next
Filter to expirations in the next fourteen days and confirm each trash, unpublish or category change is still the outcome the team wants.
Inline reschedule
Change the expiry date or the configured action across many posts at once through the standard Future save path, with the cron and audit log updated.
Audience
What Future teams use SleekView for
Editorial planning
See campaigns expiring next quarter and align them with new launches in advance, so a webinar recap is replaced rather than disappearing at midnight.
Risk reviews
Filter to expirations within seven days and confirm none of them will silently unpublish key landing pages or pricing posts on the next CMO call day.
Bulk extensions
Push every expiry on a campaign type out by a month with a single bulk inline edit when a launch slips, instead of opening each post in turn.
The bigger picture
Why a flat expiration calendar prevents real outages
Scheduled actions are powerful and dangerous in equal measure. PublishPress Future will faithfully trash a page or unpublish a post on the date you set, even if that page has, in the meantime, become the most visited content on the site. The default UI is excellent at scheduling and terrible at remembering: each action sits in its own meta box with no relationship to any other action.
A common failure mode on busy sites is a campaign page set to trash six months out, which the team forgets about, which then disappears at the worst possible moment. A flat calendar surfaces those decisions while they are still reversible. Editorial teams can do a fortnightly triage of upcoming expirations, confirm what should still fire, push obsolete actions further out and cancel the ones that no longer make sense.
That practice is much cheaper than a missing-page incident and turns Future from a quiet liability into a managed schedule.
Questions
Common questions about SleekView for PublishPress Future
No. PublishPress Future still runs the cron jobs, fires the configured actions and writes to the Future Action Log. SleekView is a faster planning view on top of the same metadata, designed for the team-level overview that the per-post meta box was never meant to provide.
It reads _expiration_date and _expiration_date_options, the canonical keys PublishPress Future uses for scheduling. The same keys persisted across the Post Expirator rename, so legacy installs work without configuration. Custom action types added through Future filters are also resolved into the action column.
Yes. Inline edits go through the same save path Future uses, which means cron is rescheduled correctly, any custom actions registered through Future filters fire as expected and the Future Action Log records the change just as if you had edited from the meta box.
Yes. A toggle includes posts whose expiry has already fired, so you can review the recent history of trashed, unpublished or category-changed posts. This is the simplest way to confirm that yesterday's scheduled actions completed and that nothing fell through the cron.
Yes. The meta keys and action shapes did not change in the rename to PublishPress Future, so any legacy Post Expirator install works without configuration. Sites mid-migration can run the audit before and after the rebrand to confirm continuity of scheduled actions.
Yes. Multi-select rows from any filtered view and clear the expiration meta in one call. The cron job for each cancelled action is removed and the Future Action Log records the cancellation, so future audits show why the schedule changed.
Yes. Custom action types added through Future filters appear as values in the action column, fully sortable and filterable. A site that registered a custom move-to-archive action can scope the table to those rows and audit them separately from built-in trash and unpublish actions.
Yes. PublishPress Future supports any post type, and SleekView mirrors that. The post type column is filterable, so a site that schedules expirations on products, events and standard posts can scope each to its own view or run a combined timeline across all of them.
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