SleekView for WP Reset Pro: snapshots and collections as tables
WP Reset Pro stores snapshots in wp_wpr_snapshots and reset history in wp_wpr_history, plus per-action metadata in wp_options. SleekView turns those rows into a sortable, filterable grid so dev teams can compare snapshot ages, sizes, and origins across a fleet.
♾️ Lifetime License available
Snapshots and reset history in a real table
WP Reset Pro keeps two custom tables that matter for operations: wp_wpr_snapshots holds each snapshot record with size, table count, and creation user, while wp_wpr_history logs every destructive action like reset, nuke, or partial reset. The default Snapshots screen shows a fixed card layout with limited sorting, which makes it slow to compare snapshot ages and storage across many sites.
SleekView reads both tables directly and renders a single grid with snapshot name, table count, size, age, and origin as first-class columns. Filters surface snapshots older than a threshold or larger than a size budget, and the history view joins to wp_users so each reset row shows who ran it. Saved views like Pre-deploy or Pre-update keep recurring tasks one click away.
Inline edits update snapshot notes and tags via the plugin's own meta keys, so the Snapshots screen sees the same labels. Bulk delete on old snapshots clears storage in one batch instead of one card at a time. Restore still routes through WP Reset Pro's own restore flow, so capability checks and confirmation prompts stay intact.
Workflow
Build the WP Reset Pro grid in four steps
Pick the source
wp_wpr_snapshots as the primary table and wp_wpr_history as a sibling view. Both expose author, action, and timestamp columns.
Compose columns
wp_users for the author column, hide internal hashes.
Save and scope per role
Edit inline or bulk-clean
Sample columns
A typical WP Reset Pro snapshot view
wp_wpr_snapshots joined to wp_users.
wp_wpr_snapshots + wp_wpr_history
| Snapshot | Tables | Size | Created | Author | Status |
|---|---|---|---|---|---|
| pre-deploy-2026-04-22 | 62 | 184 MB | Apr 22 | tom@hello.dev | Stored |
| pre-plugin-update | 62 | 182 MB | Apr 20 | alex@studio.co | Stored |
| exploration-branch | 63 | 201 MB | Mar 12 | ria@design.io | Old |
| before-nuke | 62 | 178 MB | Feb 02 | tom@hello.dev | Stale |
Comparison
Default WP Reset Pro admin vs SleekView
Default WP Reset Pro admin
- Snapshot list is a card grid with limited sorting
- No combined filter on age and size
- Reset history is a separate screen from snapshots
- Hard to spot stale snapshots eating storage
- No saved views for pre-deploy or pre-update workflows
SleekView
- Snapshots and history as joinable tables, not card decks
-
Filter
wp_wpr_snapshotsby size, age, or table count -
Show author and origin by joining to
wp_users - Bulk delete stale snapshots in one batch to reclaim storage
- Saved views for Pre-deploy, Pre-update, and Older than 30 days
Features
What SleekView gives you for WP Reset Pro
Snapshot storage view
Read wp_wpr_snapshots with size and table count columns. Sort by size to find what is eating the storage budget and by age to surface candidates for cleanup before the disk fills.
Stale snapshot filter
Save a view of snapshots older than 30 days that have never been restored. Bulk delete clears storage in one batch instead of card-by-card confirmations.
Reset audit trail
Join wp_wpr_history to wp_users so destructive actions show who ran them. Filter to reset and nuke entries to satisfy change-management evidence.
Audience
Who uses SleekView for WP Reset Pro
Development teams
Track snapshots created before deploys and feature branches. Compare table counts and sizes to spot bloat creeping in, and bulk delete stale exploration snapshots.
Operations leads
Maintain a clear pre-deploy snapshot per environment. Saved views keep the last good snapshot visible at the top of the grid, ready for one-click restore during an incident.
Agency owners
Audit how much snapshot storage each client site is consuming. Filters surface forgotten snapshots from one-off jobs, which lets the agency reclaim space instead of paying for upgrades.
The bigger picture
Why WP Reset Pro grids change operations
WP Reset Pro is a sharp tool, and like all sharp tools it punishes anyone who loses track of what is in front of them. The default card layout works for a few snapshots, but agencies and product teams who use snapshots before every deploy quickly end up with dozens of cards and no good way to compare sizes, ages, or authors. SleekView turns the snapshot table into a real grid, where size and age sort cleanly and saved views surface the last good pre-deploy snapshot at the top.
The reset history table is exposed as a sibling view so every destructive action shows who ran it, which is the evidence change management teams actually need. Inline edits to snapshot names sync back through the plugin's own meta keys, so labels stay consistent between SleekView and the Snapshots screen. Bulk deletes route through WP Reset Pro's own delete method so cloud-uploaded snapshots are removed from the configured remote as well as the local row.
Operations leads reclaim disk space without spending an afternoon on cleanup. Incident responders restore from the right snapshot the first time because the grid tells them when and by whom each one was created.
Questions
Common questions about SleekView for WP Reset Pro
Yes. SleekView queries wp_wpr_snapshots directly and surfaces snapshot name, table count, size, and creation date as first-class columns. The grid matches what the Snapshots screen shows, with richer sorting and filtering.
Yes. Restore opens the standard WP Reset Pro restore dialog with the same confirmation prompt and capability check. The plugin owns the destructive operation, SleekView owns finding the right row.
 
Yes. wp_wpr_history appears as a second view joined to wp_users, so every reset, partial reset, and nuke row shows who ran it and when. Filters narrow the audit trail to a date range or a user.
Yes. Snapshot name and notes are stored in the same row WP Reset Pro reads, so edits show up immediately on the Snapshots screen.
 
Yes. Cloud-uploaded snapshots still write a row in wp_wpr_snapshots with a storage location, and the grid exposes that column so cloud and local snapshots are filterable side by side.
Bulk delete calls the plugin's own delete method per row, so storage cleanup runs the same code path as a card-level delete. Cloud-stored snapshots are removed from the configured remote as well.
 Yes. By default only administrators see destructive options. SleekView lets you save a read-only grid for developers who need to see snapshot ages without being able to restore or delete.
 
Yes. Reset history rows live in wp_wpr_history and can be included in a CSV export filtered by user, which satisfies subject-access requests for change-log records.
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 Freshbooks Sync
- Woocommerce Facebook Feed
- Wcfm Delivery
- Woocommerce Bulk Discounts
- Alibaba Dropshipping
- Woocommerce Deutsche Post
- Woocommerce Order Export
- Product Csv Import Export
- Woocommerce Distance Rate Shipping
- Yith Woocommerce Product Add Ons
- Woocommerce Extra Product Options
- Wcfm Membership
- Skubana Wp
- Woocommerce Quick Order
- Woocommerce Quaderno