• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Plesk WPToolkit -- Cloned website is ok, what route should be used to make the clone the main website

MHC_1

Regular Pleskian
Server operating system version
alma linux 9.7
Plesk version and microupdate number
18.0.77
We have a WP website that was cloned by another developer on to a subdomain of the main.

A WordPress developer has now completed redesigning that cloned - new - website. Now we need that clone to replace the original. I can find no clear documentation on best way of
doing this?

the choice appears to be to clone the clone back on to the original , however this feels like there's lots of potential for issues (see WooCommerce note below). An alternative approach is to "Copy Data" but this also may be unwise.

What should be the best way of taking the "clone" site and replacing the "original" site with the clone data, whilst preserving elements that are aware one part is a clone and another is not.

NOTES:
- WooCommerce on the cloned copy is aware it is a copy and is in test mode.
- Documentation (via search engines) couldn't give me any useful guidance here.
 
Ok I have found that "Copy Data" seems to be the process needed. However, copying data all together has issues - copying files FIRST, and then returning to Copy Data and copying Database objects seems to do the trick. WooCommerce is as yet untested.
 
Back
Top