WP STAGING WordPress Backup Plugin – Migration Backup Restore

WP STAGING WordPress Backup Plugin – Migration Backup Restore

Backup Restore Migrate Staging Duplicator – 100% unit tested.
Rating:
4.8
star-rating-1star-rating-2star-rating-3star-rating-4star-rating-5
Active Installations:
90000+
Last Updated:
Apr 24, 2024
WordPress Version:
3.6 or higher
Tested up to:
6.5.2

Easy Backup & Cloning

Create a clone and backup of your website in seconds, perfect for staging and development purposes.

Fast & Reliable Backup

Backup and clone your website quickly and efficiently, even on weak shared hosting servers.

Seamless Migration & Transfer

Easily migrate and transfer your WordPress site to another host or domain with just one click.

Schedule Automatic Backups

Set up a daily backup plan and never worry about losing your data again.

3.5.0

  • New: Tested on WordPress 6.5.2
  • New: Add option to download and restore backup directly from cloud storage providers Google Drive, Amazon S3, OneDrive, FTP, SFTP. #1968
  • New: First release of the standalone WP Staging Restore tool. Add the constant WPSTG_ACTIVATE_RESTORER to wp-config.php if you want to test it. #2435
  • Fix: Generated create table DDL is corrupted during backup creation if table DDL contains multiple constraints with CASCADE, SET NULL, SET DEFAULT, RESTRICT or NO ACTION referentials actions. #3303
  • Fix: Backup Type missing in scheduling options. Resulting in creation of entire multisite backup even for just subsite backup on multisite. #3312
  • Fix: Resolve browser warnings due to invalid HTML syntax. #2490
  • Fix: Make sure to remove the loading placeholder after 5 seconds if the server call experiences delays or fails due to any error. #3294
  • Security: Use more secure implementation to invalidate expired login links. #3270
  • Security: Prevent accessing the system info from unauthenticated users. #3290
  • Security: Check if uploaded backup file is a valid WP Staging backup file before uploading it to the server. #3318 #3273

3.4.3

  • New: Tested on WordPress 6.5.0
  • Fix: If endurance-page-cache mu-plugin is installed (on Bluehost and Hostgator) a staging site shows white page error then. #3216
  • Fix: Backup retention does not work for backups created on a staging site. #3138
  • Fix: Backup log entries could contain log entries from staging processing under certain circumstances. #3079
  • Fix: Moved tmp directory to wp-content/wp-staging/tmp to fix a cross-device link error on sites hosted on Azure. #3213
  • Fix: Make sure that there are no errors in console after uploading backup to remote storages. #3258
  • Fix: Handle complex table relation syntax on SQL dumper and restorer. #3259
  • Fix: Validate and handle null values before invoking strlen() to ensure compatibility and prevent runtime errors. #3127
  • Fix: Make network cloning more robust by supporting different combination of www prefix. #3230
  • Fix: On some server files were not properly extracted. Using a fallback function now. #3272
  • Fix: Fix condition to check custom destination path for staging site on basic version. #3282
  • Fix: Warning “Indirect modification of overloaded elements” of WP_Hook. #3155
  • UX: Make sure the loading placeholders are rendered properly over all pages. #3207
  • UX: Beautify “license invalid” messages. #3237
  • Enh: Don’t prefix html attribute ‘data’ by ‘wpstg’. #3048
  • Enh: Add pro clone features as inactive items to Actions button in wp staging free version. #3228
  • Enh: Show error message if custom selected destination path for staging site will be same as root of live sites folder. #3204
  • Enh: Show better backup logs and warnings if backup fails. #3263
  • Dev: Add support for retrying failed tests in codeceptione2e suites. This is done to counter test flakiness. #3118
  • Dev: Update outdated code of wpstg uncomment command. #3245
  • Dev: e2e_backup_test make command was not using basic plugin when running basic tests. #3225
  • Dev: Adding improved logging. #3252
  • Dev: Make sure the debug.log is kept clean from unwanted logs when running e2e tests. #3202
  • Dev: Refactor ‘ThirdParty’ namespace changing Framework/Support/ThirdParty to Framework/ThirdParty. #3224

3.4.2

  • [skipped]

3.4.1

  • Enh: Remove files that were false-positive detected as malicious. #3184
  • Fix: Remove two css files accidentially loaded on the frontpage. #3208
  • Fix: Make sure to not encode single and double quotes while downloading log files. #3168

3.4.0

  • New: Add option to create a new admin user account for your staging site during it’s creation. #3087
  • New: Add option to use non-blocking process for uploading to FTP storage when using FTP extension for backup upload. #3103
  • New: Add advanced excludes option at WP CLI backup-create command. #3114
  • New: Add ‘Delete Settings’ button within the backup storage provider interface to facilitate the removal of the cloud provider configuration. #3108
  • New: Add support for Search Replace of urls in content of network subsites. #2960
  • New: Add option on edit staging site page for testing database connection. #3106
  • New: If uploads folder is symlinked exclude it from disk space calculation before creating a staging site. #3092
  • Enh: Update look and feel of backup scheduling modal. #3090
  • Enh: Add page loader for each page of the user interface. #3142
  • Enh: Add new upgrade buttons to header and license page. #3135
  • Enh: Add more information like database name to system information. #3125
  • Enh: Avoid scanning of excluded directories during the push and backup process. #3049
  • Fix: Fatal error on old WordPress 4.4.32 due to using of get_current_network_id(). #3174
  • Fix: Base prefix wrongly replaced for users and usermeta tables in views when creating backup of views in multisite subsite. #3128
  • Fix: Prevent error while directory listing protection due to open_basedir restriction. #3180
  • Fix: Update free version plugin meta description to “Required by WP Staging Pro”. #3171
  • Fix: Remove redundant admin notices for invalid license keys during activation. #3139
  • Security: Fix a potential security error and add better sanitizing for backup title. #3152
  • Fix: Make sure EDD license checks are triggered only once. #3179
  • Fix: Google drive authentication not working properly under all circumstances. #3156
  • Fix: Selected custom tables on a staging site that had a different prefix than the prefix in the wp-config.php could not be pushed anymore. #3170
  • Fix: Prefix for user capabilities was not replaced when creating a backup of network subsite. #3129
  • Fix: The “Prefix” field was empty for listed staging sites if they were created in an external database and the prefix was not specified. #3166
  • Fix: The optimizer setting was shown as disabled, even if it was still active. #3151
  • Fix: Add loading icon beside ‘Refresh License Status’ button and adjusted loading bars on licensing page. #3185
  • Fix: Super (network) admins were not able to login with when network subsite backup was restored on a single site. #3191
  • Fix: Reference Error wpstgPro is not defined during staging site creation on FREE version. #3136
  • Fix: Make sure that backup plugin notice doesn’t overlap Create Staging Site button in UI. #3148
  • Fix: List of active plugins in system info is misleading. #2996
  • Fix: Make sure that mail setting page looks good on all screen resolutions. #3094
  • Fix: Incorrect process modal title for preserving data task. #3130
  • Fix: DRY properties in BackupMetadata and remove error message “trying to hydrate dto errors BackupMetadata::setCurrentNetworkId()” #3199
  • Dev: Update DI52 library to latest version for small performance gain. #3146
  • Dev: Fix missing adminer host on wpstg command. #3120
  • Dev: Load Basic or Pro service provider once other dependencies are loaded. #3160
  • Dev: Populate dev hosts from env variables to add to hosts file. #3122
  • Dev: Add adminer to dev tools for database management. #3112
  • Dev: Fast test fails on GitHub due to the missing of ‘wpstgBackupHeader.txt’ file, checksum needed to be updated each time. #3110
  • Dev: Update Github actions to latest version that uses Node 20 to avoid deprecation message Github CI. #3200

3.3.3

  • New: Support for WordPress 6.4.3
  • New: Add filter wpstg.push_excluded_directories to exclude specific folders during push. #3050
  • New: Add ‘Do review link’ to backup success modal after staging site and backup creation. #3085
  • Enh: Reduce number of API calls to wp-staging.com for version number checking. #3091
  • Enh: Add option to use APPEND Mode for uploading backup using FTP from settings UI. #3044
  • Enh: Add loading icon during activation of the free version. #3041
  • Enh: Improve the message when backup has been created with older version of WP Staging. #3033
  • Enh: Make sure the checkbox icon appears at centre on all system. #2920
  • Enh: Make sure that font size and view layout is consistent in staging and reset modal. #3104
  • Fix: Can not update email address for sending error reports. #3109
  • Fix: Deprecation message about dynamic properties thrown by Google Drive Api Model class. Show exact error message when unable to get resume URI for Google Drive backup upload. #3076
  • Fix: Make sure to not check external DB credentials in free version while creating staging site. #3054
  • Fix: Editing the backup schedule sometime re-creates the schedule cron at a wrong time. #3101
  • Fix: Add filter to hide primary key changes message and include primary key details in the system information. #2972
  • Fix: Not all files are sometimes pushed under certain situation. #3082
  • Fix: Scheduled Backups unable to run when a manually created backup exists. #3089
  • Fix: The backup retention number of Google Drive backups isn’t honored. #3063
  • Fix: Handle issues when unable to fetch information for external database during cloning requirements. #3029
  • Fix: Show correct version of WP Staging in backup and staging log files. #3010
  • Fix: Type error when passing multiple parameters using hooks methods. #3064
  • Fix: Reduce height of the delete staging site modal. #3058
  • Tweak: Keep only wp-staging* plugins active during database renaming process on backup restore to avoid conflict. #3095
  • Tweak: Deprecate Filter ‘wpstg.ftpclient.forceUseFtpExtension’ as we already provide alternate option in FTP settings UI. #3053
  • Tweak: Improve success message after push about clearing site and theme cache, which may be required if the front page appears different than expected. #3003
  • Dev: Add initial level logic to support Backup Compression and Restore of Compressed Backups. #2555
  • Dev: Reduce number of manual e2e dispatch call by adding wp cli and cloud storages e2e in full PRO e2e suite and run them in parallel. #3073

3.3.2

  • Fix: Catch type errors on properties hydration for Backup Metadata and other backup related tasks. #3072

3.3.1

  • Fix: Handle warnings when unable to unserialize serialized data during cloning. #3004
  • Fix: Don’t logout when restoring backup wp.com site on last step when database was not restored. #3031
  • Fix: PHP Fatal error: Uncaught TypeError when using Litespeed server. #3060

3.3.0

  • New: Add backup and restore support for sites hosted on WordPress.com. #2433
  • New: Add input form for backup URL directly migrate a backup to another site. #2752
  • Enh: Allow to re-authenticate if current session expires during creating staging site, backup or push process. #2285
  • Enh: Show all network site host-names in system info. #2953
  • Enh: During PUSH, use temp directory outside of plugins and themes directories to avoid plugin duplication and conflicts in case of a failure. #1595
  • Enh: Refactor and DRY backup cache class. #2991
  • Enh: Show admin message if user has another backup plugin installed and tell how amazing the WP Staging feature is:-) #2966
  • Enh: Add dev filter activation. #2976
  • Enh: Don’t reload all staging sites after creating staging site for smooth user experience. #2940
  • Enh: Show better error message when cloning process stops due to memory exhaustion. #2935
  • Fix: Although all tables were renamed correctly during backup restore, the backup restore log sometimes show incorrect number of tables restored. #2974
  • Fix: Can’t serialize unserialized data that has an instance of a class in the object. Relevant for backup and backup restore. #2981
  • Fix: Make sure to execute backup performance javascript only when creating a backup. #3019
  • Fix: Installing the required free version when installing the pro version might disable all network active plugins on a multisite network. #2997
  • Fix: Improve cleaning up of cache files after pushing and backup. #3021
  • Fix: If only one file is selected for pushing, that file is not copied. #3011
  • Fix: Under rare circumstances a push could miss to copy the last file of a queue. #2901
  • Fix: On Bitnami Hosted WordPress Sites, Plugins and Themes are not replaced during PUSH due to symlinked wp-content folder. #2692
  • Fix: Undefined index of databaseSsl #2995
  • Fix: Notice “Free version required” may show up on network admin page while backup free version is not network activated. #2949
  • Fix: Don’t show “Customized uploads folder notice” when host is flywheel. #2970
  • Fix: Make sure javascript events are only registered when the corresponding element is loaded in the DOM. #3039
  • Dev: Fix reauthentication e2e when creating backup. #3006
  • Dev: Add a windows based docker setup to run all backup and staging e2e and unit tests on a real Windows environment. #2699
  • Dev: Update nodejs docker image for building and compiling assets.#3016

3.2.0

  • New: Support up to WordPress 6.4.2
  • New: Adding feature to create backup of individual network site in multisite installations. #2795
  • New: Add backup settings in backup logs. #2969
  • Fix: Automatic backup repair if the backup file index is corrupted. #2861
  • Fix: Saves remote storage backups in the database for use when calculating the number of backup to keep on remote storage. #2856
  • Fix: Prevent accessing the content of backup cache files created during cloning and pushing jobs. #2984

3.1.4

  • New: Add smart exclusion options for backup creation and allow exclusion of cache files, post revisions, spam comments, unused plugins and themes and deactivated plugins with a single click. #2758
  • New: Add ‘Refresh License Status’ button beside ‘Activate License’ and ‘Deactivate License’ button. #2809
  • New: Show modal in free version when there are performance issues after creating backup. #2721
  • New: Add option to upload already created backup to a cloud storage. This feature will be disabled by default. But can be enabled by defining WPSTG_ALLOW_REMOTE_UPLOAD constant to true. #2610
  • Enh: Formatting and cleaning up legacy backup related core/utils code. #2910
  • Enh: Improve the admin notice about the required free version during plugin installation to make it more visually striking. #2885
  • Enh: Add placeholders for pipe and colon characters in file and path names so that they can easily be extracted from backup file index. #2575
  • Enh: Disable the ‘start backup’ button when no storage is selected. #2921
  • Enh: Formatting and clean up for WPStaging PHPCS Sniff code. #2851
  • Fix: Page loading wrapper was overlapping elements on staging page. Add a loading bar below the header menu when switching between staging and backup main tabs. Adjust the delete modal! #2952 #2938
  • Fix: Exclude unused themes filter doesn’t work properly for entire multisite backup. #2927
  • Fix: Urls containing port i.e. example.com:8080 were not correctly replaced during using backup for site migration if destination site has different port. #2919
  • Fix: Due to presence of www prefix in constant DOMAIN_CURRENT_SITE on the destination site during backup restore, both source and destination weren’t considered same site for updating subsites related URLs. #2954
  • Fix: Remove Type strictness from custom wp_mail function used in staging site when mail sending is blocked to avoid “Uncaught TypeError”. #2932
  • Fix: Unable to create directory with correct permissions in ABSPATH when ABSPATH has wrong or custom permission i.e. 0170 but ABSPATH is writeable during staging site creation. #2925
  • Fix: Upsell welcome page shows up when pro is installed and free activated. #2939
  • Tweak: Show a proper message on FREE version why the backup cannot be restored if backup has same site url with a different url scheme. #2841
  • Dev: Some e2e tests were still using old checksum file for comparing plugin dist package, which leads to plugin not being latest for those tests. #2916
  • Dev: Add PHPCS rule improvements for return type hint. #2899
  • Dev: Moved backup cloud storage related e2e tests to separate suite and DRY workflows generation for e2e tests. #2951
  • Dev: Don’t run storage related tests on basic e2e backup tests. #2930
  • Dev: Add digitalocean backup dev credentials into dev doc. #2963

3.1.3

  • Fix: There was a potential security vulnerability due to which a malicious user could eventually exploit and access the wp staging cache folder. This issue is now fixed. The security issue was found by Thanks to Dmitrii Ignatyev from cleantalk.org. #2908
  • Fix: Siteground related issue: file_put_contents() doesn’t free up resource automatically immediately, which caused error 500 during backup extraction on SiteGround hosting (due to limited resources). #2868
  • Fix: For domain based subsites during backup restore, home and site_url were not adjusted properly automatically. #2857

3.1.2

  • New: Compatible up to WordPress 6.4.1
  • New: Add latest cloning, pushing, backup and backup restore logs when the user downloads the log files or opens support ticket and share debug information. #2806
  • Fix: Warnings in WordPress 6.4 because WordPress removed property $wpdb->use_mysqli. This could lead to a backup error. #2881
  • Dev: Add missing twentytwentyone theme to multi_tests to make backup tests work. #2888
  • Dev: Add a Sniff rule to check for proper use of esc_html_e in backup related code. #2875
  • Dev: Use cache and run unit tests in parallel to reduce time taken by fast backup tests. #2862
  • Dev: Fix DB version in DB seed file for multisites backup tests. #2891
  • Dev: Fix issue with WP CLI e2e backup test not running due to missing core plugin. #2896
  • Dev: Add make command to update DB backup seed files. #2893
  • Dev: Make sure that the .gitignore file remains intact and doesn’t get deleted when running ./wpstg changelog:update command. #2873
  • Dev: PHPCS rule for adding a newline after “for, foreach, if” block statements. #2831
  • Dev: Use constants for job type for cloning/pushing backup process instead of hard coding them. #2850

3.1.1

  • New: Make WP Staging compatible up to PHP 8.3 RC. #2543
  • New: Add option in settings UI to force use FTP extension over FTP curl method for remote uploading backup using FTP. #2731
  • New: Add constant WP_DEVELOPMENT_MODE with value all to new staging site. WP_DEVELOPMENT_MODE constant was added in WordPress 6.3. #2792
  • New: If the “wpstg_push_excluded_tables” filter is used to exclude tables from the push process, these tables are deactivated in the push table selection. #2776
  • Enh: Make sure pro upgrade button font color can not be overwritten by third party. #2846
  • Fix: Improve design of the “delete staging site” modal. #2843
  • Fix: Existing previously created backup files may be invalid under certain circumstances and can lead to a faulty website after restoration. This is a highly recommended update! Please create a new backup after installing this update to ensure that this potential error does not affect your backup file. #2861
  • Fix: Remove warnings in debug.log that say “WP STAGING: Another instance of WPSTAGING active…”. #2849
  • Dev: Use 7zip instead of zip to achieve better compression ratio to create smaller plugin zip packages. #2854
  • Dev: Make Flywheel e2e tests pass that were failing due to missing file in flywheel structure. #2871

3.1.0

  • New: Compatible up to WordPress 6.3.2
  • New: Exclude GoDaddy mu-plugin by default when creating a staging site. #2744
  • New: Add modal to opt-in for diagnostic monitoring after first installation. #2391
  • New: An active installation of the free core plugin will be mandatory for pro version 5.1.0 and later. #2612
  • Enh: Added information into system info logs to indicate whether the site is a single site or a multi-site. #2790
  • Enh: Show notice that permalinks won’t work on WP Engine sites. #2142
  • Enh: Add Contact Us button to the main menu bar. #2763
  • Enh: Update license updater and fix a small error that can lead to broken API requests. #2817
  • Enh: Remove type strictness from optimizer plugin functions which are used with wp hooks to avoid conflict with other plugins. #2830
  • Fix: Backup uploading to FTP fails if ftpclient is used and ssl enabled. #2750
  • Fix: Staging login doesn’t work if Wordfence Activated option exists in the database but there is no Wordfence plugin active. #2812
  • Fix: Magic login link does not work if only the free version is active on the staging site. This requires updating WP Staging Free and Pro plugin on staging site. #2781
  • Fix: Custom WP content paths inside ABSPATH were not correctly cloned for newly created staging site. This could led to missing images and languages. #2740
  • Fix: When editing staging sites database connection, don’t make live sites database prefix mandatory when staging site uses an external database. #2768
  • Fix: Deprecated warning in login form can prevent login to staging site. #2804
  • Fix: Upgrade routine was not working for wpstg_queue table for adding response field in the table for FREE version. #2828
  • Fix: During the file extraction of backup restore, file_put_contents is more consistent and faster than touch. Can prevent a site from being broken after backup restore due to possible bug in php 8.1.22. #2807
  • Dev: Add setup for e2e testing of wordpress.com support. #2739

3.0.6

  • Fix: There could be a fatal error after plugin activation on multisites if a plugin uses the filter site_option_active_sitewide_plugins. #2785
  • Fix: Theme Twenty Twenty Three has a bug that leads to corrupt staging sites. The transient _transient_wp_core_block_css_files breaks the css after migrating or creating a new staging site. This transient will be deleted on a freshly created staging site. Related: https://wordpress.org/support/topic/wordpress-block-styles-not-loading-in-frontend/ #2778
  • Dev: Add make command to check class method return type hints #2769

3.0.5

  • New: Compatible up to WordPress 6.3.1
  • New: Add support for Wordfence 2FA authentication in the WP Staging login form. #2253
  • New: Add two new filters to allow updating active plugins on staging site after cloning and on live site after pushing. wpstg.cloning.update_active_plugins and wpstg_pushing_update_active_plugins. #2409
  • Enh: Added real time elapsed time counter and restructured new staging process modals. Fixes an issue where log files are mixed up in the log window after canceling a staging process. #2651
  • Enh: Enable “Email Error Report Sending” as default in WP STAGING | PRO during initial plugin installation #2722
  • Enh: Wrap WP Staging hooks in custom methods to make WP Staging plugin(s) less exploitable. #2748
  • Fix: Php error ‘cross-device link’ can lead to backup restoring failing on Microsoft Azure servers. #2548
  • Fix: Drop-in plugins like object-cache.php and advanced-cache.php were not excluded by default during cloning. #2746
  • Fix: Exclude wp-content/wp-staging-sites directory during CLONING and BACKUP and also keep this directory during Backup Restore #2765
  • Fix: The delete confirmation modal shows a wrong staging site name when there is more than one staging site. #2741
  • Fix: Exclude All in One Security Plugin (AIOS) from being disabled by wp staging optimizer during staging or backup operations when AIOS has the post prefix option enabled as this will make wp staging unusable. #2672
  • Fix: After backup creation and backup restoring, the log entries in the success modal get purged and are not visible anymore. #2719
  • Fix: Make the batch renaming process for tables (in both RESTORE and PUSH) more robust and less error prone. #2772
  • Dev: Fix inverse usage of TaskResponseDto::isRunning #2643

3.0.4

  • New: Allow the usage of wildcards characters in the push filter ‘wpstg_preserved_options’. #2546
  • New: Exclude multiple database values from copying to a staging site table through the ‘wpstg.cloning.database.queryRows’ filter. #2545
  • New: You can add the new constant WPSTAGING_DEV_SITE into wp-config.php that determines if site is a staging/dev site or regular one. #2556
  • Fix: Cannot upload single backup files larger than 25GB on SFTP Storage. #2539
  • Enh: Removed console logs and clean up code. #2561
  • Enh: Rename logfile to wpstg-bundled-logs.txt while downloading and sending report to support team. #2593
  • Enh: Improve admin notice if cron jobs do not work. #2723
  • Fix: Fatal error due to foreign key constraints on tmp or bak tables when cleaning WP Staging tmp and bak tables before Pushing a staging site to live. #2728
  • Fix: Fatal error during backup restore if site has a drop in plugin like db.php or object-cache.php due to incorrect checking the checksum of the drop in plugin file. #2715
  • Fix: Add new constant WPSTG_MEMORY_EXHAUST_FIX, that can prevent memory exhausted errors during backup creation. #2551
  • Fix: A custom UPLOADS folder outside wp-content was not pre-selected and copied during cloning process and tustom UPLOADS folder was not copied during pushing a staging site as well. #2736
  • Fix: Improve admin notice when a pro backup is restored with the free version on another domain, host or server. #2697
  • Tweak: Adjust the requirements for restoring backup by making it dependant on backup structure instead of plugin version. #2717
  • Dev: Bump AWS PHP SDK package to latest version #2295
  • Dev: Remove PHP 5.6 compatibility code #2714
  • Dev: Reduce file size of the free plugin by removing unused backup cloud storages libraries from vendor packages. #2710
  • Dev: Add e2e tests for admin notices for backup and staging #2652
  • Dev: Delete tests output dir content while running make reset and ./wpstg build:webdriver-rebuild-dist #2726

3.0.3

  • New: Add dropbox cloud storage backup provider. #1881
  • New: Add support for custom domain based multisites. Network sites will be created in a subdomain. E.g.If the main site is “example.com” and the staging site destination url is “staging.example.com” then the live network site example.org will be cloned to staging.example.org and the network site example.net will be cloned to staging.example.net automatically. #2600
  • New: Add more options to wp cli backup backup-create command #2468
  • New: Add new contact us modal for free version to be able to provide better support to free users. #2246
  • New: Create staging site as default into ‘example.com/wp-content/wp-staging-sites/staging-site- name’ if root folder is not writable. #2438
  • Enh: Revise warnings in the symlink modal tooltip and improve the HTML syntax structure #2668
  • Enh: Transform the ‘click here’ hyperlink into a button on the staging site to enable staging site cloning #2664
  • Enh: Show admin notice on staging site if symlink option has been used to create it #2667
  • Enh: Added target URL when transferring staging site to live site #2362
  • Fix: Show admin notice on all pages on live or staging site if current site uses wpstgtmp_ or wpstgbak_ table prefixes as live table. #2666
  • Fix: Canceling the New CLONING process would delete all tables of production site if advanced settings were used to provide custom prefix for staging site with same database and host as production site. #2665
  • Fix: WP Staging backup folder gets deleted during restore on Windows OS. This can lead to an interuption and fatal error of the backup restore. #2690
  • Fix: Improve condition whether a table belongs to current site table during PUSH when cleaning temporary tables. #2686
  • Fix: If database tables prefix contains underscore like wp_12345, the sql backup part in multiparts backup is detected as separate backup. #2656
  • Fix: Having residual tables with wpstgbak_ prefix can leads to unsuccessful PUSH and backup RESTORE. Unless the current site prefix is wpstgbak_, these tables are now removed before starting RESTORE and PUSH #2576
  • Fix: Added style enhancement of changing the cursor to a pointer when interacting with the ‘Contact Us’ button #2662
  • Fix: Copied generated login link contains inline css style. #2654

3.0.2

  • New: Support for WordPress 6.3
  • New: Add more options to wp cli backup-create command #2468
  • Enh: Increase log file storing time to 14 days. #2625
  • Enh: Add admin notice to explain the new backup feature in free version #2524
  • Enh: Enhance free version backup modal UI #2608
  • Enh: Don’t allow saving empty table prefix for a staging site when using the edit button #2572
  • Fix: Use DTO instead of separate file for managing index sizes while creating backup to avoid filesystem lock. #2640
  • Fix: Backup creation fails on PHP 8 because unable to get primary key for table. #2629
  • Fix: Stop backup restore if no sql query is found to be executed but the backup contains a database to be restored #2560
  • Fix: Show admin notice if there is no WordPress table prefix in the database #2586
  • Dev: Add changelog entries in dedicated files #2623
  • Dev: No changelog needed on release branches #2763

3.0.1

  • New: Make UI more consistent and use same success and processing modals for staging site creation as for backup creation #2221
  • Fix: Rating banner can not be dismissed #2632
  • Fix: Multipart backup scheduled to be sent to google drive does not send all parts #2516
  • Fix: Could not backup tables that contain multiple primary keys (composite keys) #2616
  • Fix: Stop backup restore and add better logging if sql file is not readable during backup restore #2560
  • Fix: New delete modal does not show all tables on sites with many db tables due to CSS issue #2221
  • Fix: Resolved conflict with plugin “Admin and Site Enhancements” #2513
  • Fix: Prevent UI issue and word wrapping on line that says: “No staging site found” on MacOS on Chrome #2552
  • Dev: Undefined method interfaceDatabaseClient::fetchAll() in phpstan #2622
  • Dev: e2e tests fail on multi sites #2631

WP STAGING Backup & Cloning | Full changelog:
https://wp-staging.com/wp-staging-changelog

Would not answer basic questions

By jabbamonkey on May 2, 2024

I sent WP STAGING a question that would help me make a decision regarding purchasing their software ... they avoided answering, were rude, and said that I needed to purchase their software if I wanted "support" (note: I was asking questions about the software's capabilities, not asking for help using their software). If this is how they treat potential customers, I can only imagine how they treat their actual customers (once they already have your money). I recommend looking for solutions elsewhere.

A lifesaver

By rebop on May 1, 2024

Easy, works. Gives me a place to try Plugin updates with no concern for their failures.

most features are commercial

By Hassan1 on April 30, 2024

most features are commercial

Very comfortable!

By gatonero on April 29, 2024

This gives an extra level to test new features.

Schnell und zuverlässig und kostenlos

By buddhafoundation on April 28, 2024

Tut, was es soll und das zuverlässig. Danke für die kostenlose Version, wichtig für uns als Ehrenamtliche.

Free version doesn't allow you to test the primary function

By d2webdesigns on April 28, 2024

I typically don't write reviews because I fully understand there are a lot of nuances that could keep the software from working for someone or not doing exactly what they need, but I'm a bit tired of the bait and switch.
Yes, there is a free version... but it DOESN'T allow you to even test the staging portion of the plugin... it's primary function! You can clone the site, test the changes on the new server but not push the data back to the original site. A tiny bit of trust has to be given by the developers since we're trusting you with our data.
I will not purchase their software at $20/mo. to find out that it won't fully do what the client needs. Allow me, as a potential buyer to test all of your functions, once... twice maybe, or even for a week before locking it behind a paywall. Don't lock out it's primary functions you cannot test without making a payment.

It is not free if you need to migrate to other serve under different domain

By jaspash on April 27, 2024

It is not free if you need to migrate to other serve under different domain . You can only migrate to another hosting/server only on the same domain. Which doesn't make much sense for a Migration tool.

I get this message:

[critical] - [2024/04/27 20:54:07] - Cannot restore this backup! Free Version doesn't support site migration and can only restore backups created on the same domain, host and server. Get WP Staging Pro to restore this backup on this website.

Hostile payment options - check refund policy

By vayoka on April 23, 2024


Before making a purchase, I strongly encourage you to thoroughly review the refund policy of the software. It's crucial to understand that you must pay to test all the features, and the decision to issue a refund rests solely with the company. Should you encounter any issues where the software does not perform as advertised, be prepared for the possibility that the fault may be attributed to external factors rather than the software itself. Being well-informed about these policies can help manage your expectations and ensure that you make a decision that aligns with your needs and resources.

You get a good idea of their business practices if you read their refund policy.

Easy and useful to create playgrounds to test

By Haim (koostamas) on April 21, 2024

Great idea for testing. Simple make a copy of the website and play with it to try out new ideas. Thanks for this plugin!

Realy good Plugin and Suport

By gofreem on April 20, 2024

Very good plugin and a great team behind it. I've been using it for free all this time and eventually thought, 'It's time to finally reward the team.' The plugin is fantastic and a must-have for all website owners. Need something installed quickly? No problem. Just set up a staging site and give it a try. Then you can apply the changes directly to the main site.

Then I noticed that something could be improved and submitted a support ticket. It was answered and resolved within just one day. Respect! Keep up the good work…

Thank you from Germany

Try other plugins too!

JetBackup – WP Backup, Migrate & Restore

JetBackup is the best backup choice for WordPress. Backup, restore, clone, duplicate or migrate your website with few clicks.

Try Demo

BackUpWordPress

Simple automated backups of your WordPress-powered website.

Try Demo

WP Umbrella: Manage Multiple Sites – Ideal For WordPress Maintenance

Everything agencies and freelancers need to sell WordPress maintenance and manage multiple sites effortlessly.

Try Demo
Screenshots

Try WP STAGING WordPress Backup Plugin – Migration Backup Restore With InstaWP

Request demo

Wondering how to integrate InstaWP with your current workflow? Ask us for a demo.

Contact Sales

Reach out to us to explore how InstaWP can benefit your business.