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

Plugin Author: WP-STAGING
WordPress profile: WP-STAGING
Plugin version: 2.8.8
Last updated: September 21, 2021 (4 weeks ago)
Tested up to (WP version): WP 5.8.1
Downloaded: 0
Rating: 5 (out of 5)

Description


WP STAGING for WordPress Cloning & Migration

This duplicator, staging, and backup plugin can create an exact copy of your entire website in seconds.* Great for staging, backup, or development purposes.
(Cloning and Backup time depends on the size of your website)

This clone plugin creates a clone of your website into a subfolder or subdomain (Pro) of your main WordPress installation. The clone includes an entire copy of your database.

Note: For pushing & migrating plugins and theme files to production site, check out the pro edition https://wp-staging.com/

All the time-consumptive database and file cloning operations are done in the background. The plugin even automatically does an entire search & replacement of all serialized links and paths.

This staging and backup plugin can clone your website even if it runs on a weak shared hosting server.

WP STAGING can help you to prevent your website from being broken or unavailable because of installing untested plugin updates!

Watch this video on YouTube.

Main Features

  • WP STAGING clones the whole production site into a subfolder like example.com/staging-site.
  • Easy to use! Create a clone of your site by clicking one button
  • No Software as a Service – No account needed! All data belong to you only and stay on your server.
  • No server timeouts on huge websites or/and small hosting servers
  • Very fast – Migration and clone process takes only a few seconds or minutes, depending on the website’s size and server I/O power.
  • Use the clone as part of your backup strategy
  • Only administrators can access the clone website.
  • SEO friendly: The clone website is unavailable to search engines due to a custom login prompt and the meta tag no-index.
  • The admin bar on the staging website is orange colored and shows clearly when you work on the staging site.
  • Extensive logging features
  • Supports all popular web servers: Apache, Nginx, and Microsoft IIS
  • [Premium]: Choose a separate database and select a custom directory for cloning
  • [Premium]: Make the clone website available from a subdomain like dev.example.com
  • [Premium]: Push & migrate entire clone site inc. all plugins, themes, and media files to the production website.
  • [Premium]: Define user roles that get access to the clone site only. For instance, clients or external developers.
  • [Premium]: Migration and cloning of WordPress multisites

Note: Some features are Premium. This means you need WP STAGING | PRO to use those features. get WP STAGING | PRO!

Additional Features WP STAGING | PRO Edition

  • Backup entire website, even with millions of database rows extremely fast
  • Migrate and transfer WordPress to another host or domain
  • Cloning and migration of WordPress multisite
  • Define a separate database and a custom directory for cloning
  • Clone your website into a subdomain
  • Specify certain user roles for accessing the staging site
  • Copy all modifications from the staging site to the production website

Change your workflow of updating themes and plugins data:

  1. Use WP STAGING to clone a production website for staging, testing, or backup purposes
  2. Create a backup of your website
  3. Customize the theme, configuration, update or install new plugins
  4. Test everything on your staging site and keep a backup of the original site
  5. If everything works on the staging site start the migration and copy all modifications to your production site!

Can´t I just use my local WordPress development system like xampp / lampp for testing and backup purposes?

You can test your website locally but 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 production website exactly as you 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 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 platform only without creating a backup staging site.

This is where WP STAGING comes into play… Site cloning, backup, and staging site creation simplified and with enterprise code quality on a new level.!

Official Site

https://wp-staging.com



FAQ


Why should I use a Staging Website?

Plugin updates and theme customizations should be tested on a staging platform first before they are done on your production website.
It’s recommended to have the staging platform on the same server where the production website is located to use the same hardware and software environment for your test website and to catch all possible errors during testing.

Before you update a plugin or going to install a new one, it is highly recommended to check out the modifications on a clone of your production website.
This makes sure that any modifications work on your production 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 a production environment isn´t done very often by most users because existing staging solutions are too complex and need a lot of time to create a
an up-to-date copy of your website.

You may be afraid of installing plugins updates because you follow the rule “never touch a running system” with having in mind that untested updates are increasing the risk of breaking your site.
This is one of the main reasons why WordPress installations are often outdated, not updated at all, and insecure because of this non-update behavior.

It’s time to change this, so use “WP STAGING” for cloning, backup, and migration of WordPress websites

How to install and set up?

Install WP STAGING backup via the admin dashboard. Go to ‘Plugins’, click ‘Add New’ and search the plugins for ‘WP STAGING’. Install the plugin with ‘Install Now’.
After installation, go to WP STAGING > Staging Sites and create your first staging / backup site

Is this a backup plugin?

Even though you can use WP STAGING for backup purposes, the free version is not a usual backup plugin per the general definition. WP STAGING creates a clone of your entire website which you can immediately use for developing and testing.
You can even use it as some kind of backup in case something happens to your production site but only the WP STAGING | PRO pro version allows you to download the backup to your local computer. There are many other popular backup plugins out there but our goal is to bring the reliability and performance of a backup plugin to a new level. So instead of offering our backup feature free of charge, we think it’s time to provide a full-fledged premium backup solution with enterprise code quality affordable for everyone.

Video: How we run automated tests for WP STAGING

What is the difference between WP STAGING and other backup plugins?

Note: WP STAGING | PRO provides more advanced backup functionality which can be compared with the below-mentioned backup plugins. The speed and performance of WP STAGING’s backup feature often exceed even the biggest and well-established backup plugins.

We are now adding more and more advanced backup features to deliver what other existing backup plugins are still missing.

You may have heard about other popular backup plugins like All in one Migration, BackWPUp, BackupWordPress, Simple Backup, WordPress Backup to Dropbox, or similar WordPress backup plugins and now wonder about the difference between WP STAGING and those backup tools.
Other backup plugins usually create a backup of your WordPress filesystem and a database backup which you can use to restore your website in case it became corrupted or you want to go back in time to a previous state.
The backup files are compressed and can not be executed directly. WP STAGING on the other hand creates a full backup of the whole file system and the database in a working state that you can open like your original production website.

Even though WP STAGING comes with some backup capabilities its main purpose is to create a clone of your website which you can work on. It harmonies very well with all the mentioned backup plugins above and we recommend that you use it in conjunction with these backup plugins.

Note, that some free backup plugins are not able to support custom tables. (For instance the free version of Updraft plus backup plugin). In that case, your backup plugin is not able to create a backup of your staging site when it is executed on the production site.
The reason is that the tables created by WP STAGING are custom tables beginning with another table prefix.
To bypass this limitation and to be able to create a backup of your staging site, you can set up your backup plugin on the staging site and create the backup from that location. This works well with every available WordPress backup plugin.

I want to migrate my local website to another host

If you want to migrate your local website to an already existing production site you can use our pro version WP STAGING | PRO or a tool like WP Migrate DB which copies only the database.
WP STAGING is intended for creating a staging site with the latest data from your production site or creating a backup of it.

What are the benefits compared to a plugin like Duplicator?

We like the Duplicator plugin. Even if it is not as fast as WP STAGING for creating a backup it is a great tool for migrating from a development site to production one or from production site to development one and a good tool to create a backup of your WordPress website.
The downside is that before you can even create an export or backup file with Duplicator a lot of adjustments, manual interventions, and requirements are needed before you can start the backup process.
The backup plugin Duplicator also needs some skills to be able to create a backup and development/staging site, where WP STAGING does not need more than a click from you to create a backup or staging site.
Duplicator is best placed to be a tool for the first-time creation of your production site. This is something where it is very handy and powerful.

If you have created a local or web-hosted development site and you need to migrate this site the first time to your production domain then you are doing nothing wrong with using
the Duplicator plugin! If you need all your latest production data like posts, updated plugins, theme data, and styles in a testing environment or want to create a quick backup before testing out something then we recommend using WP STAGING instead!

If speed, performance, and code quality are a matter for you as well, give WP STAGING | PRO a try.

I can not log in to the staging / backup site

If you are using a security plugin like Wordfence, iThemes Security, All In One WP Security & Firewall, or a plugin that hides the WordPress default login URL make sure that you have installed the latest version of WP STAGING to access your cloned backup site.
If you can still not log in to your staging / backup site, you can go to WP STAGING > settings and disable there the WP STAGING extra authentication. Your admin dashboard will still be protected and not accessible to public users.

Can I activate permalinks on the staging site?

Permalinks are disabled on the staging / backup site after first time cloning / backup creation
Read here how to activate permalinks on the staging site.

Can I give you some feedback?

This plugin has been created in thousands of hours and works even with the smallest shared web hosting package.
We also use enterprise-level approved testing coding environment to make sure that the cloning and backup process run rock-solid on your system.
If you are a developer you will probably like to hear that we use Codeception and PHPUnit for our backup software.

As there are infinite variations of possible server constellations it still can happen that something does not work for you 100%. In that case,
please open a support request and describe your issue.



Screenshots:


  1. Create new WordPress staging / backup site

    Create new WordPress staging / backup site

  2. Select name for staging / backup site

    Select name for staging / backup site

  3. Select folders to include in staging / backup site

    Select folders to include in staging / backup site

  4. Cloning / backup processing

    Cloning / backup processing

  5. Listed staging / backup sites

    Listed staging / backup sites

  6. Listed staging / backup sites

    Listed staging / backup sites

  7. Open, edit & delete staging / backup sites

    Open, edit & delete staging / backup sites

  8. Login to staging / backup site

    Login to staging / backup site



Other notes:




Latest Change log entry:


  • New: Compatible up to WordPress 5.8.1
  • Enh: Refactor the wp_login action hook to work with different parameter count than the one in WordPress Core #1223
  • Enh: Sort new staging backup sites in descending order by creation time #1226
  • Enh: Warn if creating a backup in PHP 32 bit version #1231
  • Enh: Update the backup upload success message #1221
  • Enh: Show a notice if there is a new WP STAGING free version of the backup plugin #1250
  • Enh: Rename db option wpstg_existing_clones_beta to wpstg_staging_sites #1211
  • Enh: Update the warning message shown when the delete process of the staging backup site fails #1257
  • Enh: Allow use of REST API on staging backup sites without login #1287
  • Enh: Add new EDD software licensing updater for the pro version of the WP STAGING backup plugin #1294
  • Fix: New pro version does not recognize staging backup sites created with older free version #1293
  • Fix: Fix a rare issue that could happen when creating a new staging backup site or restoring a backup when there is a row with primary key with value zero #1271
  • Fix: Try to repair MyISAM table if it’s corrupt when creating a Backup #1222
  • Fix: Fix an issue on backup creation that would cause a database export to loop when encountering a table with negative integers or zeros as a primary key value #1251
  • Fix: Lock specific tables while exporting a backup, to prevent a rare duplicated row issue #1245
  • Fix: If the memory exhausts during a database export using the Backup feature, lower the memory usage/speed of the export and try again automatically #1230
  • Fix: Prevent failure of adding database to backup from causing a loop #1231
  • Fix: Fix issue when old backup clones from version 1.1.6 or lower replaces the existing clones from later version when upgrading from FREE to PRO version #1233
  • Fix: Fix inconsistent Unselect All Tables button’s action #1243
  • Fix: Replace undefined date with proper formatted date during backups for some warning and critical messages #1244
  • Fix: Split file scanning of wp-content into scanning of plugins, themes, uploads and other directories to reduce timeout issues #1247
  • Fix: Rename .user.ini to .user.ini.bak after cloning to reduce fatal errors on staging backup site. Also show a notice. #1255
  • Fix: Skip scanning the root directory if all other directories are unselected before starting a backup staging site #1256
  • Fix: Show correct insufficient space message instead of permission error if unable to copy or create a backup site due to insufficient space #1283
  • Fix: Fix showing of error when unable to count tables rows and wrap table name when fetching rows during backup #1285
  • Fix: Remove custom error handler that could cause errors due to notices being thrown #1292
  • Fix: Fix an error that would occur when PHP lacked permission to get the size of a directory when pushing a staging backup site to production #1295
  • Dev: Set the version of Selenium containers to 3.141.59-20210713 to avoid issues with broken latest version of selenium #1234


Tags:


backup, clone, database backup, duplication, 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