I developed my site in a local installation and tried to transfer it to a server, this plugin damaged my database in the local installation and the backups I made are useless for the domain server. So now I have a useless local installation that I can't repair and an online site with a broken database. Maybe it can be faster to redo the site rather than repair the damage that this plugin made to my site.
So please, don't risk your work and use a plugin of another developer!!!! This is useless and it damages the code. I even've lost money as a consequence of using this.
I have used this plugin in the past and it was excellent.
Now it seems broken under WP 4.3.1 even with all other plugins disabled. It hangs during the process of preparing to save a backup - which is fundamental. Seems like a problem with scanning the files to backup/move.
Connecting to xxxxxx:21... Success!
Logging in as xxxxx using password... Success!
Starting uploading files...
DBBackup-14288277991.sql is being uploaded... Failed!
Uploading files is completed with 1 error...
Closing the FTP connection...
Destination location exists.
So it's pretty much useless.
I wouldn't recommend this plugin for an entry level beginner of WordPress. The developer doesn't provide instructional notes and what few notes included are vague, leading my users to look for ADVANCED settings that are not there.
Very important that you accurately provide the path from the top directory that your FTP account has access to, to the backup directory of the WordPress Move plugin on the remote server.
If you get the path correct you should have no problem.
I installed this and tried to get a migration starting with Firefox. The script to display the local filestructure causes the browser to freeze so I tried again in Chrome. This time I managed to get to the transfer start however all I got for my trouble is a white screen.
no error message, no progress no log, just a white screen.
Stay away from this buggy plugin. I tried using WordPress Move to clone a test server in production. The cloned production site did not work; only the home page was functional. And it did a search/replace for the old/new domain on my the test server when I created the backup image, breaking that site, too! I was able to fix my test site with Xcloner, which is much better documented and easier to use than WordPress Move.
You must log in to submit a review. You can also log in or register using the form near the top of this page.