Release Notes for WP Staging 4.16.0

WP Staging 4.16.0 is out.

New capabilities and enhancements.

Fixes

• Backups no longer fail their own integrity check when their size lands just below a power of ten.
• Cancelling a backup started from the first-run screen now closes the progress window and offers the choice again, instead of leaving the window open and failing on a second attempt.
• Remove every leftover staging site list backup when the plugin is uninstalled.
• Delete the backups a plan no longer keeps once the new one exists, so a plan that keeps a single backup is never left without one.
• Delete the temporary copy of the staging site’s storage credentials when an update cannot restore it, and on uninstall.
• Exclude the background-processing queue table from staging site clones.
• Give the backup a plan makes with Create backup now the plan’s schedule id, so the plan counts that backup toward the number of backups it keeps, rotates it away in its turn, and reports it as its last run.
• Honour WP-CLI options written with a leading double dash and report unknown ones.
• Keep rebuilding the backup cron events when one backup plan’s schedule id is not a string.
• Keep the “Cancelling & Cleaning up” modal after cancelling a backup restore instead of reporting the job as cancelled from another page.
• Name the missing automatic login endpoint instead of blaming a firewall when the staging site runs WP STAGING Free.
• Protect updates clicked before the page finishes loading.
• Reduce temporary files created during backups.
• Refuse cloning to a target directory PHP cannot read instead of failing with a fatal error.
• Refuse creating a staging site when its destination table prefix is already in use.
• Refuse to back up a subsite in the WP-CLI backup-create command when it is archived, suspended or deleted, or belongs to another network.
• Regenerate Elementor CSS after restoring a backup or syncing a database with Remote Sync.
• Report a cancellation that cannot finish instead of asking the server about it for ever.
• Say which task could not be built instead of blaming disk space.
• Select custom folders under wp-content by default when pushing, so a push no longer leaves them behind without saying so.
• Show actionable guidance for Error 429 during backup uploads.
• Show only one label at a time on the backup “Contains” icons, instead of leaving several overlapping.
• Stop a cancelled backup, staging site or push from logging the request the cancel aborted to the browser console, and report an error a finished job runs into while it closes down instead of swallowing it.
• Stop an interrupted clone from leaving a live WordPress in the staging folder wired to the production database.
• Stop reporting a backup restore as failed when its status check fails right after pressing Cancel.
• Stop the WP-CLI backup-create command from backing up a different subsite than the one subsite_blog_id names.
• The Create Backup modal no longer opens by itself on the backup page of a site that stopped running WP Staging Pro.

New in WP Staging Pro

• Add “Create Blank WP Site” option that installs a fresh WordPress instead of cloning the live site.
• Create a full-site backup before pushing to production.
• Preview and map subsite URLs when cloning and pushing.
• Support multiple independent FTP / SFTP storage profiles per site.
• Duplicate an FTP / SFTP storage profile, so a second destination on the same server needs no retyped connection details.
• Keep FTP / SFTP destinations out of staging sites, so production credentials are not copied to a clone.
• Add opt-in low disk space mode for Remote Sync pull that creates and transfers the backup in capped parts, so the source site no longer needs free disk space for the whole backup.
• Keep the Next-Gen transfer method selected after a push.
• Make WP-CLI staging-site-create honour its database and other advanced options.
• Prevent duplicated domain suffixes and preserve escaped page-builder URLs when restoring backups.
• Stop an unchanged save of a backup plan from restarting the point its runs are counted from, so a missed backup stays reported.
• The Upload Backup to Cloud and Create Backup modals no longer reopen by themselves after saving cloud storage settings that did not leave the page.
• Record the actual reason a Remote Sync authentication failed instead of one generic message.

Full changelog: https://wp-staging.com/wp-staging-changelog/

WP Staging Pro changelog: https://wp-staging.com/wp-staging-pro-changelog/

• This topic was modified 18 hours, 25 minutes ago by Rene Hermenau.