• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue After cloning to "staging.<domain>" it keeps showing <domain>

mr-wolf

Silver Pleskian
Plesk Guru
I've used the Wordpress extension to clone a Wordpress-site to https://staging.<domain>
It created an alias, a new subfolder and a new database.

In this instance I was able to update all plugins and I recognize that staging-instance as having all plugins updated.

I have checked that new database for any occurences of https://<domain> or http://<domain>
Some of them were still there and replaced those with staging.<domain>
I also checked for any occurences of <domain> in files in that folder.
Replaced those with staging.<domain>

Still.... when I select that instance the first 3 are missing staging.

When I browse to https://staging.<domain> I'm getting redirected to https://<domain>


upload_2017-4-4_14-18-30.png
 
The same here. Anyone found a fix or workaround as a temporary solution?

Impossible to access and work on the cloned version. Checked everything - the db is correct, wp_options table links are correct, CloudFlare settings doesn`t redirect, no redirects at all.

Everything is correct but WordPress Toolkit still thinks it is a https://<domain> not https://staging.<domain> as it should.

Is this an issue or we miss something?

Edit: Plesk version: 17.5.3 Update #12; WordPress Toolkit version: 2.1.2-403

Regards
 
Last edited:
If anyone will have the same issue, for a temporary solution you can try this:
Open your staging.<domain.com> and edit wp-config.php file by adding the following lines:

Code:
define('WP_HOME','https://staging.domain.com');
define('WP_SITEURL','https://staging.domain.com');

Worked for me.
 
After we deleted the staging website, when trying to access the original domain.com/wp-admin it redirects to staging.domain.com/wp-admin

The WP Toolkit shows the original website URL as staging.domain.com/wp-admin and it is impossible to access the admin now. :)
 
Hello,

Similar issue could occur when WordPress options "siteurl" and "home" for some reason was incorrectly replaced in the database of the clone. Could you please check it directlry in database (see attached screenshot) or via WordPress administrator dashboard? Both options should have the same prefix "staging.". If it is not, it looks like a bug.
 

Attachments

  • url-options.png
    url-options.png
    218.3 KB · Views: 11
Back
Top