Plugin / WP Staging – DB & File Duplicator & Migration

Changelog

2.6.4

• Fix: Broken image folder with duplicate leading slash after cloning

2.6.3

• New Support for WordPress 5.2.4
• New: Allow wildcards for excluding files
• New: Add hook “wpstg_clone_action_staging” to execute code on staging site after cloning
• Tweak: Improved support for custom uploads folder if user customized UPLOADS constant or upload_path in DB
• Fix: Better compatibility with Windows IIS server
• Fix: External links are broken after cloning if ABSPATH is equal to /www/
• Fix: use an alternative method for file_put_contents as it is not supported on all systems due to file permission issues
• Fix: Redundant and duplicated update comments in wp-config.php in staging site

2.6.2

• Fix: Do not show warning “Preparing Data Step3: Failed to update rewrite_rules in wpstg0_options”
• Fix: Change error “Table wpstgtmp_options does not exist” to warning
• New: Add arguments for hook wpstg_cloning_complete
• New: Setup server environment variables per process and not globally (e.g. set_time_limit)
• New: Add support for custom uploads folder if user customized UPLOADS constant or upload_path in DB

2.6.1

• New: Improve styling of login form. Thanks to Andy Kennan (Screaming Frog)
• New: Add ‘password lost’ button to login form
• New: Change welcome page CTA
• New: Add feedback option when plugin is disabled
• Fix: PDO instances can not be serialized or unserialized
• Fix: Can not update staging site db table if there are constraints in it

2.6.0

• New: Compatible up to WordPress 5.2.2
• New: Performance improvement for directory iterator using less server ressources
• New: Add filter wpstg_folder_permission to set a custom folder permission like 0755, allows to overwrite FS_CHMOD_DIR if it has been defined.
• Fix: Error conditions in class Data does not compare type strict (== vs. ==) resulting in interruption of clone process
• Fix: Excluded folders under wp-content level are not take into account on microsoft IIS servers

2.5.9

• New: Update for WP 5.2.1
• New: Better corporate identity and more friendly UI colors for staging sites listings and button
• New: Better warning notices before updating process is executed
• New: Add tooltips for explaining navigation buttons
• New: Check if UPLOAD constant is defined and use this value for uploads folder destination
• New: Show notice if user tries to clone a staging website.
• Fix: Staging sites listing entries appeared on the cloned website.
• Fix: Do not search & replace through “__PHP_Incomplete_Class_Name” definitions
• Fix: Prevent wordfence firewall rule interrupting the clone deletion method
• Fix: Excluded wp staging directory from deleting process is ignored and will be deleted either way
• Fix: Strip whitespaces in cloning site internal names

2.5.8

• Fix: Remove admin notice that wp staging is not compatible with latest wp version

2.5.7

• Fix: Fatal Error: Remove previous implemented action to not search & replace over incomplete classes. This lead to high memory consumption and error 500 in step 2 of the cloning
• Fix: Cloning process interupts if there is not data to change in last step of cloning

2.5.6

• New: Compatible to WordPress 5.2
• New: Allow adding file .wp-staging to root of website to determine if it’s a staging or production website
• New: Add extended data about a staging site in list overview of staging sites
• New: Show unfinished or interrupted clones and allow deletion of them
• Tweak: Move admin notices templates to views/notices
• Fix: Rating notice appears again after using review later button
• Fix: Can not find staging site when staging site has been created with old version of wp staging
• Fix: Do not search & replace over incomplete classes in database to prevent warnings

2.5.5

• Fix: Fatal error, undefined function wpstg_validate_data()

2.5.4

• Fix: WordFence firewall rule ‘local file inclusion’ blocks wp staging initial starting cloning sequence
• Fix: Values of form Extra directories to copy are ignored

2.5.3

• Fix: Disable the WP-Spamshield Plugin on staging site because it prevents login to the staging site
• Fix: Lower the memory consumption when the cloning scan process is started
• New: Show PHP user in system info log

2.5.2

• New: Tested up to WordPress 5.1.1

2.5.1

• Fix: WP Staging > Tools > System Info does not open
• New: Open system info log file directly via wp staging > tools

2.5.0

• Fix: Do not exclude db.php if it is not located in the wp-content folder
• Fix: Select All button for DB tables not working properly
• New: Add Filter to exclude certain tables from search & replace operation
• New: Show PHP user in system info
• New: Check if there is already one process running before executing the cloning process
• New: Support up to WordPress 5.1

2.4.9

• New: Add new DB table selection manager
• Fix: Better warning notices before updating a staging site
• Fix: Stop delete process if staging site has been deleted manually before
• Fix: Log file folder does not have correct permission 0755
• Fix: Continue cloning if siteurl & home in wp_options could not be changed
• Tweak: Better warning for the update method
• Tweak: DB tables and file verification opened as default option
• Tweak: Skip rows larger than 5MB for search & replace operations to keep memory consumption low
• Tweak: clean up search & replace method
• Tweak: Better FAQ

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