Under rare circumstances, the connection between the staging and the production site may get lost, and you need to connect the staging site again with the production website.
Under WP STAGING > Sites, you will see that your staging site is not listed any longer.
The missing site’s page looks like this:
This can happen when you manually migrate your staging site to live or delete the database row containing the WP STAGING settings.
It also happens if you’ve restored your production site from an earlier backup that did not contain the latest staging site settings data.
This can also happen if you moved your production and staging site to another server.
How to reconnect the staging site after moving website.
Another reason for this could be if you created your staging site with an ancient WP Staging version like 1.6 or earlier and then upgraded to the latest WP STAGING Pro version.
If WP STAGING lost its connection to the staging site, it’s impossible to push the staging site to the production website any longer.
Reconnect Existing Staging Site with Production Site
The easiest way to fix this is to follow these steps:
- Click on the button CREATE STAGING SITE button.
- Stop the staging site process at the first step by refreshing the browser.
- You’ll see a broken/unfinished staging site.
- Go to WP STAGING Pro > Tools and search for the entry ABSPATH.
5. Copy the ABSPATH value and go to WP STAGING Pro > Sites.
6. Find your staging site and click on Edit Data:
7. Enter the target directory path ending with the name of your staging site in lowercase:
Don’t change the Database Access Data if the staging site is located in the same database.
If the staging site is connected with a separate database enter the database credentials there.
8. Click on “Save Clone Data”
Now you should be able to properly push your staging site!
Reconnect Manually By Editing the Database
If you are familiar with PhpMyAdmin and are not scared of modifying the production database, you can reconnect your staging site by changing the database’s relevant data.
As long as you change the mentioned values only, you cannot break anything. It’s still a good idea to make a backup first!
WP STAGING stores all its staging sites as serialized data in the table
wp_options and in the row with the option_name
- So, create first a new staging site!
Give it any name but not the same name as the staging site you like to connect to.
You can exclude all files and database tables to speed up the cloning process!
This will create a data set like this in the table.
Get this data and copy it.
As you can see, this data set is for a staging site with the following parameters:
- Directory location
As this is a serialized data set, you can not do a simple search & replace, and you need to follow the instructions below carefully:
- Open phpMyAdmin and look for the
wpstg_existing_clones_betain the database table
- Get the value of that column and copy it into an empty text file for backup purposes.
- The next step is to open the PHP serialized data online editor from the link below and paste the data into the input-form 1 (Paste in serialized PHP here)
- Now, change the path to the staging site in the input form 2 to your staging site’s new location!
You can get the destination by looking into the system info at
WP Staging > tools > system info and finding the value ABSPATH.
- This is the path to the root directory of your WordPress website.
Just add the subfolder name of the staging site, and you’ll get the full path to your staging site:
- Go back to phpMyAdmin and paste the modified serialized PHP data back into the field,
wpstg_existing_clones_beta.Overwrite the value and save it.
Now WP Staging is connected again to your staging site, and you can migrate your staging site to live by going to WP Staging > Sites
if you struggle with these steps, get in contact with us, and we’ll help you with it.