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

[timburkart]

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?

 

[Evgeny]

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.

 

[timburkart]

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?