• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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