Bruce Pimenta
New Pleskian
We used the clone function of the Wordpress Toolkit on some websites over the past 4 months without any noticeable issue. Users worked on those websites and updated content.
Last week we received report of sudden old content on those websites and it seems, the database has been replaced by an old version of the database (or maybe a copy of the original database). Looking into the webroot, we couldn't notice, if the files of the old version were copied as well or if those are still the same from the first clone attempt.
Additional to that, we were noticed by the Server Administration Panel (bottom right notice), that the clone of the website has been done successful - but the appropriate clones have actually been done over a week ago.
We have got the feeling, that a recent reboot of the server might have triggered this "second attempt of cloning", but so far we can only guess.
Here some specs of our system:
Linux Ubuntu 14.04.6 LTS
Plesk Onyx: 17.8.11 Update #53
Wordpress Toolkit: 4.2.2-2314
We recovered the websites from backups. As we can't reproduce it, it wasn't reported as bug for now.
Last week we received report of sudden old content on those websites and it seems, the database has been replaced by an old version of the database (or maybe a copy of the original database). Looking into the webroot, we couldn't notice, if the files of the old version were copied as well or if those are still the same from the first clone attempt.
Additional to that, we were noticed by the Server Administration Panel (bottom right notice), that the clone of the website has been done successful - but the appropriate clones have actually been done over a week ago.
We have got the feeling, that a recent reboot of the server might have triggered this "second attempt of cloning", but so far we can only guess.
Here some specs of our system:
Linux Ubuntu 14.04.6 LTS
Plesk Onyx: 17.8.11 Update #53
Wordpress Toolkit: 4.2.2-2314
We recovered the websites from backups. As we can't reproduce it, it wasn't reported as bug for now.