• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Cloning Wordperss to another domains subdomain issue

Henri Pelkonen

New Pleskian
Hi,

I think there's a bug with Wordpress cloning to another domain.

I tried to clone a Wordpress site with Wordpress toolkit to another domains subdomain to make it visible to internet by selecting existing wordpress subdomain.domain installation from the cloning destinations.

The cloning overrided the the domain main parent wordpress installation and didn't clone to the the subdomain wordpress installation as expected so the main site got destroyed by the proccess!

So the installation is now in vhosts/domain/httpdocs/wordpress and not in vhosts/domain/subdomain.domain/wordpress.
 
Last edited:
Hello,

I were not able to reproduce such an issue.
I've tried to do this in the following way:
1. I have a subscription with the following configuration:
- domain.tld - with WordPress installation placed at vhosts/domain.tld/httpdocs/
- subdomain.domain.tld
- addondomain.tld - with WordPress installation placed at vhosts/domain.tld/addondomain.tld/
2. I've cloned WP instance from addondomain.tld with destination "existing domain or subdomain subdomain.domain.tld"
As a result I've got three WordPress instances:
- domain.tld - with WordPress installation placed at vhosts/domain.tld/httpdocs/ which were not changed after the clone operation
- subdomain.domain.tld - with a clone of addondomain.tld placed at vhosts/domain.tld/subdomain.domain.tld/
- addondomain.tld - with WordPress installation placed at vhosts/domain.tld/addondomain.tld/
WP instance at domain.tld (vhosts/domain.tld/httpdocs/) were not changed.

Could you please provide more details if you have configuration which differs from my?
 
Hi, and thanks for the reply and your time,

I must test also with new domain and double check my configuration and let's see if the problem recurs or not.
 
Hi!
I found the reason and it was that a subdomain's document root was pointing at the main domain's document root because of a earlier wordpress multisite configuration. My bad and now the sites cloned fine :) Mayby a visual clue of the to be cloned site's new document root path before confirmation would be helpful for someones forgetting their settings like me?
 
Thank you for your investigation.
I've forwarded this information to an appropriate person. It looks like a good idea to show source and destination paths, as document root may be customized.
 
Back
Top