• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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