• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Why are plugins updated in cloned site also updated in parent site?

timburkart

New Pleskian
Server operating system version
CloudLinux 8.10.0
Plesk version and microupdate number
cPanel 124.0.10
I cloned my main site, example.com to stage1.example.com. The cloned site lives at public_html/stage1.example.com. The problem is that all updates to the stage site are also made to the main site. How can I prevent this from occurring?
 
Could you explain, what you did and what & where you saw?

If you mean that you changed any WordPress things and see them in another WP - the root cause may be in any specific caching plugin that shares cache between the both WP.
If you update plugins via uploading a new version into global plugins tab - this update is visible for all your sites.
Also would be nice to check that plugins are truly updated (check plugin's file) because you may see cached shared plugins info, for example.
 
Could you explain, what you did and what & where you saw?

If you mean that you changed any WordPress things and see them in another WP - the root cause may be in any specific caching plugin that shares cache between the both WP.
If you update plugins via uploading a new version into global plugins tab - this update is visible for all your sites.
Also would be nice to check that plugins are truly updated (check plugin's file) because you may see cached shared plugins info, for example.
I updated a plugin on the stage site but when I go to the plugins page on the parent site, it shows the newer version. There is no caching plugin on either site. I checked the file dates for both the parent and cloned site. What I saw is that the plugin on the parent site was updated but not the cloned site. This tells me that the plugin update on the cloned site actually updated the parent plugin. Why would that be?
 
Since the site was cloned, WP Toolkit works with 2 different sites and works with them separately and does not sync the state automatically.
What I saw is that the plugin on the parent site was updated but not the cloned site.
at this time, I can imagine only one way to get it: the plugin was updated on the wrong site by human mistake.
for example: you can have 1 site, click clone and expect that the second site' card is a cloned site(but it is the parent because WP Toolkit puts a new installed/cloned/etc site at the top of the sites list.), go to the plugin's tab and update plugins. After page refresh, sites list becomes ordered differently and you see the parent site on the first place, and the cloned on the second.

Also you can check action logs(in UI) of the both sites to know what was happened with the sites. Plesk WP Toolkit 5.4 Release: Action Log, wp-cron Management Workflow, SSL Support, and More
The action logs provides information whom & what & when did with the site via WP Toolkit.
 
Back
Top