Requires PHP: 5.3 A duplicator plugin! Clone, duplicate and migrate live sites to independent staging and development sites that are available only t
This cloning and staging plugin is well tested but work in progress.
If you find any issue, please open a support ticket.
Note: For pushing & migrating plugins and theme files to live site, check out https://wp-staging.com/
WP Staging for WordPress MigrationThis duplicator plugin allows you to create an staging or development environment in seconds*
It creates a clone of your website into a subfolder of your main WordPress installation including an entire copy of your database. This sounds pretty simple and yes it is! All the hard time-consumptive database and file copying stuff including url replacements is done in the background.
I created this plugin because all other solutions are way too complex, overloaded with dozens of options or having server requirements which are not available on most shared hosting solutions. All these reasons prevent user from testing new plugins and updates first before installing them on their live website, so its time to release a plugin which has the potential to be merged into everyone´s wordpress workflow.
* Time of creation depends on size of your database and file size
WP Staging helps you to prevent your website from being broken or unavailable because of installing untested plugin updates!
Note: WordPress 5.0 will be shipped with a new visual editor called Gutenberg. Use WP Staging to check if Gutenberg editor is working as intended on your website and that all used plugins are compatible with that new editor.
- Easy: Staging migration applicable for everyone. No configuration needed!
- Fast: Migration process lasts only a few seconds or minutes, depending on the site's size and server I/O power
- Safe: Access to staging site is granted for administrators only.
- Admin bar reflects that you are working on a staging site
- Extensive logging if duplication or migration process should fail.
- New: Compatible to All In One WP Security & Firewall
What does not work or is not tested when running wordpress migration?
- WordPress migration of wordpress multisites (not tested)
- WordPress duplicating process on windows server (not tested but will probably work) Edit: Duplication on windows server seems to be working well: Read more
Change your workflow of updating themes and plugins data:
- Use WP Staging for migration of a production website to a clone site for staging purposes
- Customize theme, configuration and plugins or install new plugins
- Test everything on your staging site first
- Everything running as expected? You are on the save side for migration of all these modifications to your production site!
Why should i use a staging website?
Plugin updates and theme customizations should be tested on a staging platform first. Its recommended to have the staging platform on the same server where the production website is located. When you run a plugin update or plan to install a new one, it is a necessary task to check first the modifications on a clone of your production website. This makes sure that any modifications is working on your website without throwing unexpected errors or preventing your site from loading. (Better known as the wordpress blank page error)
Testing a plugin update before installing it in live environment isn´t done very often by most user because existing staging solutions are too complex and need a lot of time to create a up-to-date copy of your website.
Some people are also afraid of installing plugins updates because they follow the rule "never touch a running system" with having in mind that untested updates are increasing the risk of breaking their site. I totally understand this and i am guilty as well here, but unfortunately this leads to one of the main reasons why WordPress installations are often outdated, not updated at all and unsecure due to this non-update behavior.
I think its time to change this, so i created "WP Staging" for WordPress migration of staging sites
Can´t i just use my local wordpress development copy for testing like xampp / lampp?
Nope! If your local hardware and software environment is not a 100% exact clone of your production server there is NO guarantee that every aspect of your local copy is working on your live website exactely as you would expect it. There are some obvious things like differences in the config of php and the server you are running but even such non obvious settings like the amount of ram or the the cpu performance can lead to unexpected results on your production website. There are dozens of other possible cause of failure which can not be handled well when you are testing your changes on a local staging platform.
This is were WP Staging steps in... Site cloning and staging site creation simplified!
I just want to migrate the database from one installation to another
If you want to migrate your local database to a already existing production site you can use a tool like WP Migrate DB. WP Staging is only for creating a staging site with latest data from your production site. So it goes the opposite way of WP Migrate DB. Both tools are excellent cooperating eachother.
What are the benefits compared to a plugin like Duplicator?
At first, i love the Duplicator plugin. Duplicator is a great tool for migrating from development site to production one or from production site to development one. The downside is that Duplicator needs adjustments, manually interventions and prerequirements for this. Duplicator also needs some skills to be able to create a development / staging site, where WP Staging does not need more than a click from you. However, Duplicator is best placed to be a tool for first-time creation of your production site. This is something where it is very handy and powerful.
So, if you have created a local or webhosted development site and you need to migrate this site the first time to your production domain than you are doing nothing wrong with using the Duplicator plugin! If you need all you latest production data like posts, updated plugins, theme data and styles in a testing environment than i recommend to use WP Staging instead!
I need you feedback
This plugin has been done in hundreds of hours to work on even the smallest shared webhosting package but i am limited in testing this only on a handful of different server so i need your help: Please open a support request and describe your problem exactely. In wp-content/wp-staging/logs you find extended logfiles. Have a look at them and let me know the error-thrown lines.
Permalinks are disabled on the staging site because the staging site is cloned into a subfolder and permalinks are not working on all systems without doing changes to the .htaccess (Apache server) or nginx.conf (Nginx Server). Read here how to activate permalinks on the staging site.
How to install and setup?
Install it via the admin dashboard and to 'Plugins', click 'Add New' and search the plugins for 'Staging'. Install the plugin with 'Install Now'. After installation goto the settings page 'Staging' and do your adjustments there.
- I can not login to the staging site If you are using a security plugin like All In One WP Security & Firewall you need to install latest version of WP Staging. Go to WP Staging > Settings and add the slug to the custom login page which you set up in All In One WP Security & Firewall plugin.
- New: Compatible to WP 4.9.5
- New: Allow to select and copy extra folders that are on the root level
- New: Use fully custom login form to prevent access denied issues on sites where access to wp-login.php is denied or redirection plugins are used
- Fix: Incorrect login path to staging site if WordPress is installed in subdirectory
- Fix: Login url is wrong if WP is installed in subfolder
- Fix: If PHP 5.6.34 is used, the cloning process could be unfinished due to use of private member in protected class
- Tweak: Only wp root folders are pre selected before cloning is starting
- Tweak: Change WP_HOME or WP_SITEURL constants of staging site if they are defined in wp-config.php
- New: Replace even hardcoded links and server path by using search & replace through all staging site database tables
- New: New and improved progress bar with elapsed time
- Fix: Cancel cloning does not clean up unused tables and leads to duplicate tables
- Tweak: Wordings in rating admin notice
- Tweak: Better error messages
- Tweak: Open staging site in same window from login request
- Fix: Set meta noindex for staging site to make it non indexable for search engines
- Fix: Change default login link to wp-admin
- Fix: Unneccessary duplicates of wpstg tables in db
- Fix: Undefined property: stdClass::$loginSlug
- New: Option to set Custom Login Link if there is one
- New: Set meta noindex for staging site to make it non indexable for search engines
- New: Better multiple folder selection. Allows to unselect a parent folder without collapsing all child folders
- New: Sorted list of folders to copy
- Fix: Can not login to staging site if plugin All In One WP Security & Firewall is used
- Fix: Staging site not reachable because permalinks are not disabled under certain conditions
- Fix: Old staging site is not listed and pushing is not working properly if plugin is updated from wp staging version 1.6 and lower
- New: Performance improvement increase db query limit to 5000
- New: Detect automatically if WordPress is installed in sub folder
- Tweak: Tested up to WP 4.9.4
- Fix: Updating from an old version 1.1.6 < to latest version deletes the staging sites listing table
- Fix: Reduce memory size of the logging window to prevent browser timeouts
- Fix: Can not copy db table if table name contains the db prefix multiple times
- Fix: Some excluded folders are not ignored during copy process
- Fix: mod_security is causing script termination
- Fix: Skip directory listings for symlinks
- Fix: Increase the max memory consumption
- Tweak: Return more human readable error notices
- Fix: Cloning process stops due to file permission issue
- Fix: Exclude WP Super Cache from copying process because of bug in WP Super Cache, see https://github.com/Automattic/wp-super-cache/issues/505
- New: increased speed for cloning process by factor 5, using new method of file agregation
- New: Skip files larger than 8MB
- Fix: Additional checks to ensure that the root path is never deleted
- New: Compatible up to WP 4.9.1
- Fix. Change link to support
- Fix: Missing files in clone site if copy file limit is higher than 1
- Fix: Link to the staging site is missing a slash if WordPress is installed in subdir
- Tweak: Allow file copy limit 1 to prevent copy timeouts
- New: Add more details to tools->system info log for better debugging
- New: Add buttons to select all default wp tables with one click
- New: Show used db table in list of staging sites
- Fix: Delete staging site not possible if db prefix is same as one of the live site
- Fix: Edit/Update clone function is duplicating tables.
- Fix: Other staging site can be overwritten when Edit/Update clone function is executed
- Fix: Several improvements to improve reliability and prevent timeouts and fatal errors during cloning
Complete changelog: https://wp-staging.com/changelog.txt
- Download the file "wp-staging.zip":
- Upload and install it via the WordPress plugin backend wp-admin > plugins > add new > uploads
- Activate the plugin through the 'Plugins' menu in WordPress.
Step 1. Create new WordPress staging site
Step 2. Scanning your website for files and database tables
Step 3. WordPress Staging site creation in progress