SleekView for PublishPress Revisions Pro: pending revisions as tables
PublishPress Revisions Pro stores pending changes as draft copies under wp_posts (post_type=revision) with workflow postmeta. SleekView reads the same records and turns the queue into a grid where author, target, and approval state are filterable columns.
♾️ Lifetime License available
Revision queue in a real grid
PublishPress Revisions Pro saves every editor change to a published post as its own revision row in wp_posts (post_type=revision), with workflow metadata in wp_postmeta (status, scheduled publish time, requesting user, approver list). The default Revision Queue lists rows as a flat WP_List_Table with limited filters, so a busy editorial team ends up alt-tabbing between the queue and each parent post to figure out context.
SleekView reads the same posts and postmeta and exposes parent title, parent type, requesting user, target status, scheduled publish, and approver list as first-class columns. Filter to revisions waiting on a specific approver, sort by scheduled publish, or pin a saved view of overdue revisions per channel.
Inline edits route through PublishPress Revisions's own approval helpers, so approving or rejecting from the grid fires the same hooks as the default UI: email notifications, scheduling, and parent updates all behave identically. Bulk approve, bulk reject, and bulk reschedule turn a backlog into a sustainable workflow.
Workflow
From revision queue to editorial workspace
Connect the revision source
wp_posts filtered to post_type=revision with PublishPress Revisions postmeta keys. The grid auto-joins to parent posts and to wp_users.
Compose editorial columns
Save views per channel
Approve, reject, or reschedule
Sample columns
A typical Revisions queue view
wp_posts (post_type=revision) + wp_postmeta
| Parent title | Type | Requester | Target status | Scheduled | Approval |
|---|---|---|---|---|---|
| Spring campaign launch | post | alex@studio.co | publish | Apr 26 09:00 | pending |
| Pricing page rev | page | mia@brew.coop | publish | Apr 24 18:00 | approved |
| Knowledge base entry | kb | tom@hello.dev | publish | Apr 25 12:00 | pending |
| Retired guide | post | ria@design.io | draft | Apr 23 16:00 | rejected |
Comparison
Default PublishPress Revisions Pro admin vs SleekView
Default PublishPress Revisions Pro admin
- Queue screen sorts by date, but not by scheduled publish or approver
- No combined filter for requester plus parent post type
- Each revision opens its own screen to see the approver list
- Bulk approve works inside a single post type only
- Overdue revisions are not surfaced as a distinct state
SleekView
-
Joins
wp_postsrevisions to their parents and shows parent title and type - Filter by requester, approver, target status, or scheduled date
- Sort by scheduled publish to surface what is going live next
- Bulk approve, reject, or reschedule across any filtered selection
- Saved views per editorial channel or per content type
Features
What SleekView gives you for PublishPress Revisions Pro
Approval queue
Pin a saved view of revisions awaiting your approval. The grid groups by parent type and sorts by scheduled publish so the urgent ones stay on top of the list.
Schedule clarity
Sort by scheduled publish across every post type. Editorial leads see the next 48 hours of incoming changes in one grid instead of one screen per type.
Bulk reschedule
Filter to a campaign tag, select all related revisions, and shift the scheduled date in one bulk action. Every edit fires PublishPress Revisions's normal hooks.
Audience
Who uses SleekView for PublishPress Revisions Pro
Editorial managers
Filter to revisions waiting on their approval. Group by requester to balance load across the team and reschedule items in bulk when a launch shifts.
Section editors
Pin a saved view scoped to their own section and content type. Inline-approve from the row menu without opening each revision separately.
Production leads
Sort by scheduled publish across post types to plan the next 48 hours of go-live activity. Bulk reschedule when a launch slips.
The bigger picture
Why editorial queues deserve a real grid
Editorial workflows live or die by the queue. PublishPress Revisions Pro already captures the right data: every pending change is a real revision row, the workflow state lives in postmeta, scheduled publish times are stored where they should be. The plugin's default queue screen handles a small team well.
Once a publication has multiple sections, multiple custom post types, and multiple approvers per piece, that single screen starts to creak. Editors lose track of what they own. Production leads cannot see across sections in one view.
Approvers spend half their time clicking through to each revision to find the scheduled date. A real grid changes that. Filters compose, sorts mean something, saved views match how the team actually works.
The schedule for the next 48 hours becomes one sorted view. An approver's outstanding list becomes one filter chip. Bulk reschedule turns a slipped launch from a panicked half-day into a five-minute fix.
Nothing new gets stored; the existing data finally gets the working surface it deserves.
Questions
Common questions about SleekView for PublishPress Revisions Pro
Yes. SleekView queries wp_posts for post_type=revision rows that PublishPress Revisions created, and joins to wp_postmeta for workflow status, scheduled publish, requester, and approver list.
Yes. The row menu has Approve and Reject actions that call PublishPress Revisions's own approval helpers. Hooks for notifications, scheduling, and parent updates fire exactly as they would from the default UI.
Yes. Any post type registered with revisions enabled and tracked by PublishPress Revisions appears in the grid. Filter by parent type to scope to one custom post type at a time.
Yes. Multi-select revisions and use bulk reschedule. SleekView updates the _revision_scheduled postmeta and any related rows the plugin uses, all wrapped in the plugin's own hook.
Yes. The Approval column shows current status, and a sub-column lists assigned approvers from PublishPress Revisions's per-revision metadata. You can filter to revisions assigned to a specific user.
Two editors trying to approve the same revision see a soft conflict warning. The grid uses a short row lock and reloads the latest state before committing the action, so the last writer is never silently overwritten.
Yes. Apply your filters first, then export to CSV. The export ships exactly the visible columns, which keeps editorial reports compact and free of internal-only fields.
Yes. SleekView reads whatever wp_posts rows the multilingual plugin creates, including translated revisions. Filter by language code (when one is stored as postmeta) for per-language queues.
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 checkoutBrowse more
- Woocommerce Authorize Net Cim
- Woocommerce Side Cart
- Mailchimp For Woocommerce
- Woocommerce Ebay Integration
- Woocommerce Taxify
- Woocommerce Australia Post Pro
- Woocommerce Pricing Deals
- Edd Amazon S3
- Curcy Multi Currency
- Shipment Tracking
- Woocommerce Product Vendors
- Woocommerce Back In Stock
- Woocommerce Product Csv Import
- Yith Woocommerce Points And Rewards
- Woocommerce Xero