✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for WP Staging Pro

WP Staging Pro handles cloning, push-to-live, and backups in one plugin. SleekView reads that combined history and renders it as a sortable grid where each operation type can be filtered, audited, and compared.

♾️ Lifetime License available

SleekView table view for WP Staging Pro

Clones, pushes, and backups belong on a grid

WP Staging Pro writes job history to wp_options rows and logs detail to wp_wpstg_queue_jobs on Pro installs, with files in wp-content/uploads/wp-staging. The plugin's history screen lists jobs page by page, but a clone, a push-to-live, and a backup all appear in the same stack with similar formatting. When a redesign sprint adds twenty clones, last week's nightly backup is hard to find without scrolling.

SleekView reads the same records WP Staging Pro writes and renders them as a real WP Admin grid. The Action column distinguishes Clone, Push, Backup, and Restore; the Destination column splits Local clones from external uploads; the Duration column makes a 22-minute push-to-live next to a 4-minute clone obvious. Filters and saved views replace the linear scroll with a queryable dataset.

The grid is also where you spot a Push that completed without actually moving the files. WP Staging Pro records job state, but the dashboard does not surface a Push that finished in three seconds because it short-circuited. A saved view sorted by duration ascending pinned to outcome equals Success catches that anomaly in the same triage pass as a Failed clone.

Workflow

From WP Staging Pro jobs to a sortable run grid

1

Read job records

SleekView reads the wp_options entries WP Staging Pro writes plus the wp_wpstg_queue_jobs table on Pro installs. The on-disk logs in wp-content/uploads/wp-staging stay where they are.
2

Separate actions

Action column distinguishes Clone, Push, Backup, and Restore. Reports stop blurring four operations into one timeline.
3

Save the failure inbox

Filter to outcome equals Failed or Slow in the last 14 days, save the view, and that becomes the triage queue without anyone setting reminders.
4

Drill into logs

Click a row to open the WP Staging Pro log file for that run. The grid finds the right log; the plugin still owns its content.

Sample columns

WP Staging Pro runs

Each clone, push, backup, and restore with size and outcome.
Source: wp_options job records plus wp_wpstg_queue_jobs and files in wp-content/uploads/wp-staging
Array Array Array Array Array Array
Array Array Array Array Array Array
Array Array Array Array Array Array
Array Array Array Array Array Array
Array Array Array Array Array Array

Comparison

WP Staging Pro admin vs SleekView

WP Staging Pro

  • History page is paginated, not filterable
  • Clones and backups blur together in one stack
  • Push-to-live jobs lack a duration trend view
  • Failures hide inside per-job log files
  • No saved view for restore-readiness audits

SleekView

  • One row per clone, push, backup, or restore
  • Filter by action type to separate sprints from nightly schedules
  • Saved view for failures and slow runs in the last 14 days
  • Sort by duration to spot push-to-live regressions
  • Click through to the original job log

Features

What SleekView gives you for WP Staging Pro

Action separation

Clone, Push, Backup, and Restore on one timeline, but separable by action type. Reports stop blurring four operations into one stack.

Push duration trends

When a push-to-live creeps from 6 minutes to 22, the grid sees it first. Saved views catch regressions before they break the deployment window.

Failure inbox

Failed and Slow runs stack at the top of a saved view until someone triages them. The 0 MB Drive push stops being a silent failure.

Audience

For ops, devs, and agencies

Site reliability

Prove nightly backups ran cleanly across Local and Google Drive. Filter to action equals Backup and outcome equals Success; everything else is noise this morning.

Release engineers

Audit every push-to-live this sprint. The Action and Duration columns make it obvious which pushes need a postmortem and which were clean.

Agencies

Bring clone, push, and backup history into one grid per client site. One license, one pane of glass, no per-site reporting integrations to wire up.

The bigger picture

Why clone and backup history needs separate filters

WP Staging Pro's strongest feature is that it does cloning, push-to-live, and backups in one plugin, and that strength is also what makes its history hard to read. A clone is a sprint operation, a push is a release operation, and a backup is a reliability operation. They share machinery and they share log format, but they answer different questions.

A push hidden in three weeks of nightly backups is hard to find when release engineering asks how last Tuesday's deploy went. A nightly backup hidden among twenty clones during a redesign is hard to find when reliability asks whether last Sunday's archive ran. SleekView makes the distinction trivial by exposing the action type as a filter column.

Filter to Push to audit a release window, filter to Backup to audit a reliability week, filter to Clone to audit a sprint. Same plugin, same dataset, three different ops realities, finally separable.

Questions

Common questions about SleekView for WP Staging Pro

No. WP Staging Pro owns the clone engine, the push handshake, and the backup archive build. SleekView reads the history WP Staging Pro writes and renders it. The split keeps the staging plugin canonical and the observability layer purely read-only.

 

From the wp_options entries WP Staging Pro writes for each job, the Pro wp_wpstg_queue_jobs table, and the per-job log files in wp-content/uploads/wp-staging. No reindex, no second store.

 

Partially. The free WP Staging plugin writes a subset of the records Pro writes, so most columns populate. Pro-only features like Push to Live and external cloud destinations only appear if Pro is active because they are the ones that create those job types.

 

We recommend pruning through WP Staging Pro itself so files, archives, and metadata stay aligned. SleekView can hide rows visually with a filter, but deleting records should go through the plugin so on-disk files do not orphan their job metadata.

 

Yes. Each subsite has its own WP Staging Pro records and its own SleekView pointed at its own history. Cross-subsite reporting works the same way it does in WP Staging Pro itself: switch subsite, or roll up CSV exports per network admin.

 

None. SleekView paginates and queries on demand, and the wp_wpstg_queue_jobs table stays small even on agency sites with two years of clone history. Queries finish in well under a second on typical hosting.

 

Indirectly. WP Staging Pro does not write a row for a schedule that never fired, so a missed night looks like a gap rather than a row. A saved view sorted by Started descending makes that gap visible without a synthetic missed-run record.

 

No. SleekView reads destination names and job metadata, but never the credentials WP Staging Pro uses to talk to Google Drive, Amazon S3, or other remotes. Credential management stays in the plugin's settings, where it belongs.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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