• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Wordpress Toolkit clone: overwrites database (again) later?

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.
 
Update: just found out, that some pages had the old version before the server-reboot, so that was most probably not the trigger.
 
Back
Top