Stay FAR away.

  • 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.

Viewing 2 replies - 1 through 2 (of 2 total)

  • I’ll admit that the instructions that come with this plugin leave a little bit to be desired. But once I figured out what was missing it took only a few seconds to resolve.

    The secret is that WPM only adjusts all references to the URL. But despite asking in the setup screen for ftp details, it doesn’t (or at least in my case, didn’t) copy or move any files. I had to do that manually. And as soon as I did, everything started working correctly.

    Plugin Author Mert Yaz?c?o?lu

    (@merty)

    I am sincerely sorry that things did not work out well for you. However, proper use of WordPress Move does not lead to breaking of the original site. I see some people are having trouble finding the documentation or claiming the instructions are not clear enough. I agree and I plan to rewrite the documentation from the scratch.

    It actually does move the files. If it did not give any errors during the migration, regarding transferring files, then probably your files reside somewhere in your new server. The reason why they are not where they should be is because of the incorrect Remote Backup Path provided which is a confusing piece of setting indeed.

    Thanks for your feedback, much appreciated!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Stay FAR away.’ is closed to new replies.