Sep 242018
 
wp staging
WordPress Plugin Name: WP Staging – DB & File Duplicator & Migration
Plugin URL:https://wordpress.org/plugins/wp-staging/

Plugin Author: WP-Staging
WordPress profile: WP-Staging
Plugin version: 2.5.2
Last updated: March 14, 2019 (1 week ago)
Tested up to (WP version): WP 5.1.1
Downloaded: 0
Rating: 5 (out of 5)

Description


This cloning and staging plugin is well tested and 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 the pro version https://wp-staging.com/

WP Staging for WordPress Migration

This 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.

Main Features

  • 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.

    More safe:

  • 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:

  1. Use WP Staging for migration of a production website to a clone site for staging purposes
  2. Customize theme, configuration and plugins or install new plugins
  3. Test everything on your staging site first
  4. 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.

Important

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.

Official Site

https://wp-staging.com



FAQ


  • 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.


Screenshots:


  1. Step 1. Create new WordPress staging site

    Step 1. Create new WordPress staging site

  2. Step 2. Scanning your website for files and database tables

    Step 2. Scanning your website for files and database tables

  3. Step 3. WordPress Staging site creation in progress

    Step 3. WordPress Staging site creation in progress

  4. Finish!

    Finish!



Other notes:




Latest Change log entry:


  • New: Tested up to WordPress 5.1.1


Tags:


clone, cloning, duplication, migration, staging

+ Jason's Comments

 

Disclosure: Some of the following links are my affiliate referral links to a third party service, if you click on the link and purchase the item, I might receive a commission. In many cases, I have a developer license and can upload the theme for you, otherwise you would need to purchase a license, and if you use my referral link, I could apply the commission to upload the theme for you. Please contact me to assist you.

How can you avoid breaking your live website when updating plugins or trying out some code changes? Make a copy of your site using WP Staging and test the changes on the staging copy. After testing you could do the same changes to the live site or if there are too many changes you will need to push the changes from the stage site to the live site, which requires some effort. Alternatively, the WP Staging PRO version will automate the push to live process for you.

How to Move Over Complete Staging Site to Production

Requirements for this tutorial:

  • One live site which is in production use e.g. https://host.com
  • One staging site which you previously created with WP Staging or WP Staging Pro.
    Staging site should be located in a subfolder like https://host.com/staging
  • Plugin WP Staging activated on live site
  • Plugin Better Search Replace activated on live site
    (Not needed for WP Staging Pro)
  • Plugin BackWPup (or any other backup software) used on live site

wp staging

Top