Hey @arviman,
Sorry you ran into issues… That is very strange , nobody has ever mentioned that in the entire life of the plugin. Can you be more specific about your steps? Did you try to create a package or are you running the installer? “Ran a Backup” has several connotations…
If you run the installer and choose the option to “Connect and Remove all Data” then it will remove all data from the current database your connecting to. However this is very clear in the installer and will not let you continue until you check the checkbox labeled “The remove action will delete all tables and data from the database!”
As far as creating a package this technically is not possible because there is no delete logic anywhere when a package is created. Can you be more detailed about your steps, it sounds like you may have not read all the instructions and warnings when running the installer.
Thanks!
Hi @cory Lamle, thanks for responding. I tried to create a package. This process was successful and produced a zip file. After this, I had activated the “wordpress SEO by Yoast” plugin, but took no other action with that plugin.
After this, I had gone into “posts” and checked that the latest revisions had been lost. I checked the DB and all rows in the “Posts” table in the DB after 27-september had been lost. Actually, it appears that the DB has been reverted to a snapshot of my wordpress as it was on 27th as my theme had changed as well.
I definitely did not select “connect and remove all data” as I still retained some data (other than the last date). Does the plugin attempt to modify the current “snapshot” at any point? Sorry if I can’t provide any more descriptions.
Hey @arviman,
Thanks for the clarification! So basically you never ran the installer, which means what you described above technically could never happen with the Duplicator. When a package is created the read from the database is completely a read-only operation. I’m confident that if you went and edited a few posts and even created a few, then created another package you would not be able to see any loss of data or change from what you previously did…
You said you had activated the SEO plugin. The chances of a plugin like that causing issue would be greater as it is more tightly integrated with posts. I can’t say for sure or not if that was what caused your particular issue, however I can with 110% certainty say that creating a package would never ever cause you to ever loose data, there is just no logic in the code that could do that…
I’m certain that something else happened in your system that caused the loss of data and it happened to be circumstantial that you created a package at the same time. I hope you reconsider you vote because it doesn’t accurately reflect the real root cause of your issue.
Thanks~
Ok. Thanks for the update. The only reason I believe this plugin’s duplication caused the issue instead of the SEO-plugin activation was that the package I had did not contain the new posts. This would not be the case had the SEO-plugin deleted the revision, since I did it after the backup. I will however, update the vote to a 3* since there is not 100% evidence that points to Duplicator causing the issue.
I will retest the plugin and update the vote accordingly later since it might have been something I did wrong last time I ran it.
Thanks for that update…
That is a bit odd, to honest I’m not quite sure what is happening on the server. There has to be some other routine/theme/plugin/cron-job/cached page or series of events that are happening. When you create a package it will only read from the DB and write the SQL results to a file along with zipping up the files you requested. There is no logic anywhere that performs a write to any of the tables described…
If for some reason you run into the issue again please submit a support ticket to lifeinthegrid.com/support and I’ll help you diagnose your issue and help you find the real root cause.
Thanks
Actually, this happened again (sort of). I tried to copy to my remote server and the version that got generated was again from Sep. 27.
I didn’t lose any data in my local server (i think i must have somehow reinstalled it accidently the last time), so the issue isn’t a write but a snapshot read issue. It think it just freezes on the moment of install of the plugin.
That is very strange… There must be something setup on your site/server or something about how mysql is caching the data. When the package is created it pulls directly from a live copy. This has never been reported by anyone else in over 800k downloads… I’m puzzled as to why it would happen…
