• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

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