- Plesk Onyx
Note: This article has the reference to the issue with the fix available:
- #EXTWPTOOLK-1773 "Cloned WordPress installations should no longer share their cache with the source installation (we know sharing is caring, but not this time)."
- WordPress Toolkit 3.6.0 21 February 2019
staging.example.com is a cloned WordPress instance from example.com.
Any change made in configuration or content of staging.example.com (for example via WordPress Admin > Posts) automatically affects the original site.
There is a caching plugin like Memcachy installed on example.com.
When cloning was performed, plugin was cloned too, and both sites has the identical cache IDs. Such plugins should be disabled during the cloning, therefore it is a bug in WordPress Toolkit extension #EXTWPTOOLK-1773 that is planned to be fixed in future extension updates.
Until a fix becomes available, disable caching plugin. There are multiple ways of doing it, for example via WordPress admin dashboard.
Below is resolution via renaming the plugin file for memcachy plugin only:
Log into Plesk.
object-cache-memcached.phpfiles in Domains > example.com > File Manager > httpdocs > wp-content to