The video below shows how WP STAGING | PRO pushes data from the staging site to the production one.
WP STAGING | PRO can push all media files, the theme, plugins, and all database data from a WordPress staging website back to a production site.
Insights: To get a fundamental technical understanding of how WP STAGING moves your Staging Site to Production site and to learn the differences between files and database data, read the articles below:
– How Does WP STAGING Handle WordPress Migration
– The WordPress database structure
If you want to copy the data from the staging site to the production site, you have two options:
You can either repeat the operation you did on the staging site manually on the production site or use WP STAGING | PRO’s database migration feature, which is included in the Push Changes feature.
如何將 Staging 網站覆蓋上 Production 網站
Requirements for this tutorial are:
- The live site which is in production use, e.g.
https://example.com - The staging site which you’ve previously created with WP STAGING.
- Plugin WP STAGING | PRO installed on the production site.
步驟 1：備份 Production 及 Staging 網站
I recommend creating a full site backup with WP STAGING | PRO.
To do this, click on Backup & Migration > Create New Backup.
Enter a name and start the backup process by clicking on Start Backup.
Then save a local copy of the backup to your computer via
Actions > Download.
步驟 2：備份 Production 及 Staging 網站
Go to your Production Site > WP STAGING > Start / STAGING
If you have more than one staging site, select the one you want to transfer to the production site and click on the Push Changes button.
Push Changes Button
Note that any table chosen will overwrite its pendant on the production site completely.
If you want to exclude specific data from being overwritten on the production site, unselect the particular database table from the selection.
Check out the link below to learn more about WordPress core tables and find out which data is available in a certain table.
Note: If you like to use WP STAGING only for testing plugins and theme files before updating them on the production site, you do not need to push any database tables at all necessarily. Update the plugin and theme files on your staging site using WordPress’s internal automatic plugin updater.
If the updates are working well on the staging site, use the Push Changes button, and all plugins and themes are pushed and copied to the production site.
On the other hand, plugin and theme settings are stored in the database of WordPress. Also, database-based operations like creating new posts, assigned menus, putting widgets to a new place, changing and saving plugin or WordPress-related settings are stored in the database. Installing a new plugin is also a database operation.
So, if you do not want to recreate all settings on the production site, you need to push the database tables, too.
步驟 3：選擇 Plugins, Themes, 以及媒體檔案
Click on Select Files and choose all plugin, media & theme folders containing the data you like to copy over to the production website.
You can also define extra folders you like to move to the production site by adding the full absolute path to the text area.
步驟 4：進階選項
There are a few extra options that you can use.
- Uninstall all plugins on the production site …
- Delete wp-content/uploads folder …
These options help you to ensure that your production site will contain only the files that are existing on the staging site when you execute the push process.
For example, you uninstall a specific plugin on the staging site or delete an image. Then you can choose if you want to get this plugin and image deleted on the production site as well.
If you keep these options disabled, nothing on the production site will be deleted and the particular plugin and image will still be available. In the case of a plugin, the plugin then will be deactivated only.
步驟 5：開始執行［PUSH］
Click on Push Staging Site to Live Site, and the push process starts.
When the push process is done, reload your website, and you’ll see all the new content on your production site.
Note: WordPress sometimes requires you to log in again after a full push.
That’s it; you are done.