WP Staging – DB & File Duplicator & Migration

Beskrivning

WP Staging for WordPress Migration & Cloning

This duplicator plugin allows you to create an exact copy of your entire website for staging or development purposes in seconds.
(Exact time depends on the size of your website)

It creates a clone of your website into a subfolder of your main WordPress installation including an entire copy of your database.

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

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

This plugin works even on the smallest shared hosting servers.

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

Note: WordPress 5.x has been 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

  • No SASS service. All data belongs to you and stays on your server.
  • Easy to use! Just install it and click on ”CREATE NEW STAGING SITE”.
  • No server timeouts on huge websites or/and small hosting servers
  • Staging website will be available from example.com/staging-site
  • Very fast – Migration process takes only a few seconds or minutes, depending on the website’s size and server I/O power.
  • Only administrators can access the staging website. Login with the same credentials you use on your production site.
  • SEO friendly: The staging website is unavailable to search engines due to a custom login prompt and no-index header.
  • The admin bar on the staging website will be orange colored and shows clearly that you work on the staging site.
  • All database tables will be duplicated and get a new prefix beginning with wpstg(int)_.
  • As default the staging website will be copied into a subfolder.
  • Extensive logging features
  • Supports all main web servers including Apache, Nginx, and Microsoft IIS
  • [Premium]: Choose a separate database and select a custom directory for cloning
  • [Premium]: Make the staging website available from a subdomain like dev.example.com
  • [Premium]: Push & migrate plugins and themes to production website.
  • [Premium]: Define user roles that should receive access to the staging site only. For instance, clients or external developers.
  • [Premium]: Migration and cloning of WordPress multisites

Note: Some features are Premium. Which means you need WP Staging Pro to use those features. You can get WP Staging Premium here!

  • New: Compatible with WordFence & All In One WP Security & Firewall

Additional Features WP Staging Pro Edition

  • Cloning and migration of WordPress multisites
  • 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 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 theme, configuration, update or install new plugins
  4. Test everything on your staging site
  5. If everything works on the staging site start the migration and copy all 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 before they are done on your production website.
It’s recommended having 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 live 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.

Some users 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.
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 and migration of WordPress websites

Can´t I just use my local wordpress development system like xampp / lampp for testing 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 which can lead to unexpected results later 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.

This is were WP Staging jumps 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 an 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 each other.

What are the benefits compared to a plugin like Duplicator?

At first, I really the Duplicator plugin. It is a great tool for migrating from a development site to production one or from production site to development one.
The downside is that Duplicator needs adjustments, manually interventions and requirements 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 web-hosted 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 your 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 your feedback

This plugin has been done in hundreds of hours to work on even the smallest shared web hosting package but I am limited in testing this only on a handful of the different server so I need your help:
Please open a support request and describe your problem exactly. In wp-content/wp-staging/logs you find extended logfiles. Have a look at them and let me know the error-thrown lines.

Viktigt

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, go to the settings page ’Staging’ and do your adjustments there.

Official Site

https://wp-staging.com

Skärmdumpar

  • Step 1. Create a new WordPress staging site
  • Step 2. Scanning your website for files and database tables
  • Step 3. WordPress Staging site creation in progress
  • Finish!

Installation

  1. Download the file ”wp-staging.zip”:
  2. Upload and install it via the WordPress plugin backend wp-admin > plugins > add new > uploads
  3. Aktivera Tillägget under ”Tillägg” i menyn i WordPress.

Vanliga frågor

  • I can not log in to the staging site
    If you are using a security plugin like All In One WP Security & Firewall you need to install the 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.

Recensioner

15 oktober, 2019
Works perfect, easy to handle and allows to test chnges without influencing the main side. Great support from the developer.
13 oktober, 2019
Did the job well with the help of this plugin, very easy to use.
7 oktober, 2019
I created a staging website in less than 5 minutes and I'm usinig it to test a lot of different features before going online. Great plugin!
4 oktober, 2019
This plugin is a live changer. I can confidently test new plugin or theme updates on a perfect staging site. I am also very happy to experience continuous development with significant improvements. Keep up the excellent work!
Läs alla 1 229 betyg

Bidragsgivare och utvecklare

”WP Staging – DB & File Duplicator & Migration” är programvara med öppen källkod. Följande personer har bidragit till detta tillägg.

Bidragande personer

”WP Staging – DB & File Duplicator & Migration” har översatts till 1 språk. Tack till översättarna för deras bidrag.

Översätt ”WP Staging – DB & File Duplicator & Migration” till ditt språk.

Intresserad av programutveckling?

Läs programkoden, kika på SVN-filförvaret eller prenumerera på utvecklarloggen via RSS.

Ändringslogg

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