Also, if I try to convert the database to import it in phpMyAdmin, I get the following error message. Hope this helps.
Warning: Invalid argument supplied for foreach() in D:\Hosting\9857582\html\development\wp-content\plugins\wordpress-move\libs\functions-database-backup.php on line 40
I am having this same issue. Did you ever find out the cause of the problem?
Thank you 🙂
Developer never got back to me. I would have liked to make it work but I had to resort to manual processes. Maybe you can add something to the post to get him to respond.
gregweed, I’m really sorry for any inconvenience I caused but unfortunately I did not see this topic until now.
lnmo and gregweed, are you using any plugin that creates and uses its own database tables? If so, this might be related to the other bug that some people are reporting lately which I will hunt down and fix as soon as possible.
Once again, gregweed, I’m really sorry for that.
Mert, not a problem. I do like your plugin and I hope we can get it working.
To answer your question, yes, I believe I am using a plugin that has it’s own database tables. The plugins that I am using are…
– Contact Form to DB Extensions
– Fast Secure Contact Form
– Quick Stats
– Simple Ads Manager
– W3 Total Cache
– WordPress Donation Plugin with Goals and Paypal IPN by NonprofitCMS.org
– WP-Mail-SMTP
I tried deactivating all of the plugins and then running your plugin but I still had the same errors. If you have any questions or would like to do some testing, please let me know.
Thanks for your replay
Most probably, that is the reason then. WordPress Move seems to be unable to back up the tables that plugins create. I will find the cause of this bug and fix it as soon as possible. Some other users seem to be experiencing the same problem as well.
Thanks for your contribution in finding the bug, much appreciated!
Hi Guys,
Thank you Mert for the plug-in, it’s enormously useful and a great idea.
I found a manual work around for the problem in the end although I am working on a client site that is littered with a long list of random plug-ins, I don’t think any of them are creating db tables of their own. I’m not massively experienced with SQL stuff in general but when I log into phpMyAdmin I can see there is only the standard 11 tables that WP creates on installation.
When I was trying to figure out a workaround I did notice that the backup .sql file that had been transmitted to the new installation was very slightly smaller than the same file on the original server where it had been generated by the plugin. On seeing this I simply used ftp to manually grab that one single .sql file from the original installation and overwrite the received version on the new installation. Once I’d done that, the updated (now matching) file size was reflected in the ‘completing migration’ page and I could check just that file and complete the migration process with no further issues.
I hope that’s in some way useful.
Looks like the function that creates the database backup needs some serious attention.
Thanks for sharing your experience, it is indeed useful 🙂
