SleekView for Revive Old Posts Pro: share queue & logs as tables
Revive Old Posts Pro writes its scheduled share queue to wp_revive_old_posts_queue and its delivery log to wp_revive_old_posts_logs. SleekView surfaces both as filterable tables with platform, post, scheduled-at, and status columns.
♾️ Lifetime License available
Share queue and delivery logs as one operational table
Revive Old Posts Pro recycles published WordPress content to social platforms on a recurring schedule, with the queue and delivery history stored in custom tables (wp_revive_old_posts_queue, wp_revive_old_posts_logs) and per-account credentials in wp_options. The default admin shows scheduled jobs in a paginated list per account, with no cross-account view of which post is queued where and when.
SleekView joins the queue and log tables to wp_posts and the account map, exposing one row per scheduled or delivered share. Columns include post title, target platform, account label, scheduled time, status, and the share URL once delivered. Filters like 'failed in last 7 days', 'Twitter only', or 'post category equals news' become first-class chips rather than per-screen navigation.
Edits route through the plugin's own queue handler where it offers one (rescheduling, cancelling, retrying a failed share) and fall back to direct row updates with a conflict warning on the columns the plugin treats as immutable. The view is an operations layer alongside Revive's own admin, not a replacement for the connect-account workflow.
Workflow
From per-account screens to one share table
Pick the source
wp_revive_old_posts_queue and wp_revive_old_posts_logs. The agent reads the column list and proposes a default join to wp_posts and the account map.
Compose columns
Scope per role
Edit inline and bulk-update
Sample columns
A typical Revive share queue view
wp_revive_old_posts_queue and wp_revive_old_posts_logs to wp_posts so each row carries the post title and the target account.
wp_revive_old_posts_queue + wp_revive_old_posts_logs + wp_posts
| Post | Platform | Account | Scheduled | Status | Share URL |
|---|---|---|---|---|---|
| Guide to onboarding | @studio | Apr 24 09:00 | Shared | twitter.com/studio/1801 | |
| Pricing update post | Studio Page | Apr 24 10:30 | Queued | ||
| Founder essay | Studio Page | Apr 23 14:00 | Failed | ||
| Product launch recap | @studio | Apr 22 11:15 | Shared | twitter.com/studio/1788 |
Comparison
Default Revive Old Posts Pro admin vs SleekView
Default Revive Old Posts Pro admin
- Queue and log screens are per account, with no cross-platform unified table
-
wp_revive_old_posts_logsis paginated and not directly filterable by post category - Failed shares need to be opened one row at a time to see the error string
- No bulk-reschedule across multiple posts in one action
- Connected-account audit (which tokens belong to which platform) lives in a separate settings page
SleekView
- Unify queue and logs across every connected account in one filterable table
-
Filter by
status,platform, scheduled window, or post category in one click - Reschedule or cancel multiple queued rows at once via bulk actions
-
See the exact API error string from
wp_revive_old_posts_logsinline on each failed row - Pivot to an accounts view that lists every token, platform, and last-success timestamp
Features
What SleekView gives you for Revive Old Posts Pro
Queue plus log in one grid
Joins wp_revive_old_posts_queue with wp_revive_old_posts_logs so scheduled and delivered shares live in one row history per post, no tab switching between queue and history screens.
Cross-account filters
Filter by platform, account, status, or post category at the same time. Catch every failed Twitter share in the last 24 hours across all connected handles in a single chip combination.
Bulk reschedule and retry
Select queued or failed rows and reschedule, cancel, or retry in one bulk action. Edits route through the plugin's queue handler so cron timing and retry counters stay consistent.
Audience
Who uses SleekView for Revive Old Posts Pro
Social managers
Triage the upcoming-share queue across every account by day, ensure the launch week is balanced, and reschedule conflicts before they go out. The grid replaces five per-account screens.
Support and ops
Filter to status equals failed and read the exact error string from wp_revive_old_posts_logs inline. Token expiries, rate-limit hits, and revoked permissions all surface in one queue.
Editors and analytics
Group delivered shares by post and platform to see which evergreen posts get reused most. The same join the plugin uses for the front-end report is exposed as a sortable column set.
The bigger picture
Share queues live in the database; admin UIs hide them
Recurring social sharing is a high-volume, low-visibility operation. A single editorial site can have hundreds of scheduled shares per week across Twitter, LinkedIn, Facebook, and Mastodon, all sitting in wp_revive_old_posts_queue and quietly dispatched by cron. The default admin shows them per account, paginated, with no cross-platform view.
That is fine for a one-person blog and badly wrong for any team that cares about which posts get re-shared, when, and to whom. SleekView treats the queue as a first-class operational dataset, joinable to the post catalogue, filterable by status and platform, exportable for reporting. Social managers see the week's outgoing shares balanced across accounts.
Support filters to failed in the last 24 hours and triages token expiries before they cascade. Editors see which evergreen posts get reused and which are dead weight in the queue. None of this is new data; it has always been in those two tables.
The grid is what makes it usable.
Questions
Common questions about SleekView for Revive Old Posts Pro
No. The plugin still owns the cron job that picks the next item from wp_revive_old_posts_queue and pushes it to the platform API. SleekView only reads and writes the queue and log rows, so the actual share dispatch is unchanged.
Yes. The view joins to wp_term_relationships and wp_terms so category, tag, and any custom taxonomy on the source post becomes a column or filter. Useful for 'only reshare from /news/' style operational rules.
On multisite, Revive's tables exist per blog and SleekView reads the current blog's prefix. For network-wide audits, you can saved-search the same view on each site, or define a SleekView that unions across wp_2_revive_old_posts_queue and similar prefixed tables.
Past-shared rows in wp_revive_old_posts_logs are treated as immutable history by the plugin. SleekView marks them read-only by default and surfaces an explicit override for admins, with a warning that direct edits won't change what was already posted to the platform.
Queue and log tables stay narrow even on busy sites. SleekView paginates server-side and uses indexed columns (status, scheduled_at, account_id) so a hundred-thousand-row log queries in under a second on a typical Kinsta or RunCloud install.
No. Tokens live in wp_options under Revive's option keys and SleekView treats them as read-only. The accounts view surfaces label, platform, last-success timestamp, and last-error code without exposing the token string itself.
Yes. CSV export honors current filters and excludes the token columns by default. Personal-data export and erasure paths still go through Revive's own handlers and WordPress core, not through the SleekView grid.
Yes. Retry actions push the row back through Revive's queue handler, which respects per-platform rate limits and the plugin's configured retry policy. SleekView doesn't bypass the rate-limit logic the plugin already implements.
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 Waitlist
- Woocommerce Wholesale Gateway
- Woocommerce B2b Suite
- Veeqo Wp
- Printify Integration
- Woocommerce Loyalty Program
- Yith Woocommerce Points And Rewards
- Woocommerce Zip Checkout
- Woocommerce Snapchat Pixel
- Woocommerce Fulfillment
- Atum Inventory Management
- Woocommerce Purchase Order Gateway
- Woocommerce Octobat
- Woocommerce Name Your Price
- Cart66 Cloud