Release v6.13.1
Wp Staging Pro v6.13.1
Latest versionWhat's new in v6.13.1
Wp Staging Pro v6.13.1 was released on . Features: Cloning - Create a clone of your website with a simple click Push Changes - Copy Plugins, Theme & Media files from Staging to Live site Authentication - Staging Site is available for auth... See the full changelog below and compare with the complete version history.
Release details
Released
3.6 MB
File available
Changelog
Added
- Back up a staging site automatically before you update it, so an update that goes wrong can be undone. (Pro) #1873
- Repair a damaged backup from the command line. Everything still readable is written into new backup files you can restore. (Pro) #2255
Other
- Enh: Describe the command line tool by what it does for Developer and Agency plans: pull a live site to your computer with one command. #6031
- Enh: Never delay an update on a staging site. A staging site is where updates are meant to be tried out. #6028
- Enh: Plugin updates now start the moment you click update. The recovery backup runs behind them and a panel in the corner reports it. #6028
- Enh: Rename the free plugin on WordPress.org so people searching for a backup plugin find it. #5205
- Enh: Run backups and cloud uploads through the same background engine, so a long job is less likely to be interrupted. #5950
- Enh: Switch Update Protection off in one click from that panel. A backup the updates are waiting on is cancelled with it. #6028
- UX: Make WP Staging Desktop easy to find on the Staging screen. Developer and Agency plans get a link beside the local site action, every other plan a discovery card. The label under the local site button reads "CLI" where that link sits next to it. #6046
- Dev: A
Fixed
- A restore no longer breaks sites whose plugins link database tables to one another. #5244
- Block backups and restores on PHP versions we have not tested yet, starting with PHP 8.6. #5494
- Create and push a staging site faster on tables whose rows hold a lot of data. #5986
- Delete only the tables that belong to the staging site when it lives in its own database. #6088
- Delete the temporary plugin folders a restore leaves behind once they pile up, instead of letting them fill the disk. #1598
- Ignore tampered entries in the active plugin and login session lists while pushing. (Pro) #5411
- Keep cloud storage credentials out of System Info and the log files, and check the storage settings before they are saved. #6001
- Keep the licence section and other status messages visible when the Disable WP Notification plugin is active. #5880
- Keep the list of plugins a push has to restore even when no plugin is active on the staging site. (Pro) #5411
- Name the actual folder paths in the error a restore shows when it cannot move files, on every host. #5943
- Name the operation that is actually running when Remote Sync is blocked, instead of always saying a sync is already in progress. #5456
- Never delete a table of the live site during database cleanup, and handle table names that contain special characters. #6005
- Never delete a table of your live site when a staging site is deleted or its creation is cancelled. #6088
- 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. #2063
- 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. #5986
- Report a background job that failed on PHP 8, including a failure on the source site during a Remote Sync pull. #5967
- Report a finished backup as finished on PHP 7.0 to 7.3, so the staging site update waiting for it can carry on. #6118
- Save the FTP/SFTP settings when an SSH key is already stored. (Pro) #5920
- Show an unexpected server response as plain text, so markup inside it cannot run in the WordPress admin. #5990
- Show what is wrong with cloud storage settings in the page itself, where the message stays readable, instead of in a browser tooltip. (Pro) #5039
- Start a backup from the Remote Sync window without having to close it first. (Pro) #5063
- Stop a cancelled staging job writing an error into the browser console. #6011 #5613
- Stop a fatal error on the staging site when the login form cannot start up. #6079
- Stop an error when the progress window is closed while a job is still reporting into it. #6049
- Stop backup, restore and Remote Sync logs repeating every line, which duplicated entries and made the log files far larger than they should be. #5330
- Switch the database's foreign key checks back on after deleting tables, even when the previous setting could not be read. #6019
- Update the Start Upload button as soon as a cloud storage is selected. (Pro) #5950
- 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. #6061
- WP Staging Free now says the daily backup runs at 12:00 midnight, not noon. #6018
- Wait as long as the cloud storage asks for when it limits the upload rate, instead of failing the upload. (Pro) #6038
- Write settings and user data safely to the database when pushing, so an unusual value cannot change the query it is written with. (Pro) #5411
Improved
- Show the background option only when a backup is being created. #6085
Compatibility
- Requires WordPress
- 3.6+
- Tested up to
- 7.1
- Requires PHP
- 7.0
Verified safe
Wp Staging Pro v6.13.1 scanned clean with no security threats detected.
View full scan report