• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Resolved Plugin path not corrected/re-written during cloning process

ArmReu

New Pleskian
Server operating system version
Ubuntu 20.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.49_build1800230110.16 os_Ubuntu 20.04 with WP Toolkit version: 6.1.2-7079 (Web Admin Edition)
When creating a clone of a wordpress site the plugins path is not corrected/re-written during cloning process. It always stays the same as in the original site, even if you are cloning into a different subdomain or even full domain. Files are copied correctly, just the correction of the plugins files path for the new clones seems to be not working.

This is a real problem as it for example makes plugin update testing of dev sites impossible or even worse "disables" all plugins when cloning into a new top leven domain due to the limited access to files outsite of the wordpress installation within the server.

This is a newly created issue as a result of my futher investigation of this post
 
Update and appologies:

It turned out all the trouble were simply caused by a custom added define( 'WP_PLUGIN_DIR' ...) in wp-config.php which had a fixed path in it.

So I guess it is not really a problem of the cloning process. Yet perhaps the devs should be informed that this variable definition might cause problems and should be checked for during cloning.

@Mods: Issue can be closed
 
Back
Top