Release Notes for WP Staging 4.13.1

WP Staging 4.13.1 is out.

New capabilities and enhancements.

Highlights

• Never delay an update on a staging site. A staging site is where updates are meant to be tried out.
• Plugin updates now start the moment you click update. The recovery backup runs behind them and a panel in the corner reports it.
• Switch Update Protection off in one click from that panel. A backup the updates are waiting on is cancelled with it.

Fixes

• A restore no longer breaks sites whose plugins link database tables to one another.
• Block backups and restores on PHP versions we have not tested yet, starting with PHP 8.6.
• Create and push a staging site faster on tables whose rows hold a lot of data.
• Delete only the tables that belong to the staging site when it lives in its own database.
• Delete the temporary plugin folders a restore leaves behind once they pile up, instead of letting them fill the disk.
• Keep cloud storage credentials out of System Info and the log files, and check the storage settings before they are saved.
• Keep the licence section and other status messages visible when the Disable WP Notification plugin is active.
• Name the actual folder paths in the error a restore shows when it cannot move files, on every host.
• Name the operation that is actually running when Remote Sync is blocked, instead of always saying a sync is already in progress.
• Never delete a table of the live site during database cleanup, and handle table names that contain special characters.
• Never delete a table of your live site when a staging site is deleted or its creation is cancelled.
• Offer to carry on with a restore when the database refuses a table that has two automatic timestamp columns (MySQL error 1293), instead of stopping.
• Replace the site address in every row of a table when creating or pushing a staging site, including when the database search and replace limit is set low.
• Report a background job that failed on PHP 8, including a failure on the source site during a Remote Sync pull.
• Report a finished backup as finished on PHP 7.0 to 7.3, so the staging site update waiting for it can carry on.
• Show an unexpected server response as plain text, so markup inside it cannot run in the WordPress admin.
• Stop a cancelled staging job writing an error into the browser console.
• Stop a fatal error on the staging site when the login form cannot start up.
• Stop an error when the progress window is closed while a job is still reporting into it.
• Stop backup, restore and Remote Sync logs repeating every line, which duplicated entries and made the log files far larger than they should be.
• Switch the database’s foreign key checks back on after deleting tables, even when the previous setting could not be read.
• Use the correct table prefix when pushing with the Classic engine, keep the Desktop link inside its banner, and allow a backup to be cancelled only once preparation has finished.
• WP Staging Free now says the daily backup runs at 12:00 midnight, not noon.

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

• This topic was modified 2 weeks, 2 days ago by Rene Hermenau.