WordPress Move 1.3

7 Replies

After 2,5 months, I finally released WordPress Move 1.3 yesterday. There are actually so many things I am planning to add but I don’t want to rush and cause a huge mess. I really enjoy developing it and thinking how to make it simpler and easier to use. There are much more capable solutions than WordPress Move but I think most of them (if not all of them) are way more complicated than they should be. I will always do my best to keep WordPress Move a simple, capable and free solution for migration purposes.

Changelog for 1.3

  • Explanation for Change Domain Name is rephrased.
  • Simple and Advanced Migration methods are merged.
  • Meta boxes are added to the migration page.
  • A database backup converter is integrated to convert WordPress-Move-only database backup files to generic SQL files.
  • Backup files to use for restoration can now be selected right on the Restore page.
  • Empty HTML files are added to backup directories to prevent them being listed by people trying to access the directory via their browsers.
  • James

    Mert,

    I just want to thank you for creating this plugin. WordPress Move is seriously a dream come true. When I read the description of the plugin, it sounded too good to be true…but it worked super well, and was really simple to operate. Thanks so much, you really made my day.

    • mert

      Thank you very much for your nice words, much appreciated :)

  • http://- TLS

    Hi,

    We have tested WordPress move on several installations and looks excellent however one issue that we have is that it doesnt migrate all Tables when the Plugin Magic Fields is being used. It misses two tables, although does migrate approx. 6 other Magic field tables which is perculiar. We have tested several times but always with the same result.

    thanks.

    • mert

      A few other users also told me that they are having issues similar to yours with plugins that uses additional tables. Looks like the function that generates the database backup is somehow unable to export certain types of tables.

      Thanks for the feedback, I will have a look at this issue as soon as possible.

  • http://jmeb.co.uk James

    Hi Mert,

    Thanks for the great plugin. It looks really easy to use but I’m having a couple of problems.

    As a practise, I’ve moved a dummy installation supportyourshorts.com from one server to another. I couldn’t get the ‘Migrate’ option to work. It returned a 404 error. Instead, I backed it up using your tool and manually moved the files, and used your ‘Restore’ option on the 2nd server.

    After changing the dns, the front page is appearing, but try and click on a post or a page and you get this message:

    [an error occurred while processing this directive]

    What am I doing wrong?

    Many thanks

    • mert

      This problem is not related to WordPress Move actually. Your migration was a success.

      Please contact your host and tell them you are getting the message [an error occurred while processing this directive]. They can inspect your logs and find the real cause easily.

  • http://twitter.com/BFMTweeter Best French Mortgage

    Hi Mert, I’ve just discovered a bug – I think. Let me explain what has happened:

    1. I created a new version of a wordpress site in a test instalation located in public_html/a.com/beta/wordpress installation.

    2. When the site was ready for launch I used WordPress move to move the site on the same server to a new location public_html/b.com/wordpress instalation.

    3. Everyting has seemed fine for about 45 days

    4. Yesterday I noticed that someone had reblogged a shortcode from a Twitter account linked to b.com. For no reason I clicked the shortcode to see what the user would see and the shortcode produced a 404 error.

    5. I checked what was going on and the shortcode points to a.com/beta/correct post ID not to b.com.correct post ID.

    6. It looks as though when WordPress move moved the site it did not change the default location of the shortcode generator so though the post IDs are correct they all point to the wordpress installation that was used to create the site a.com/beta/

    The problem I now have is that ther has been around 45 days work on the site since it was moved and the site has subsequently been moved to a different host (UK2 > TSOHost) so I can no longer go back to a backup and try the move again.

    Can you suggest wht I need to do to identify exactly where the error is and correct it?

    Incidentally, I can no longer get WordPress Move to run on the new TSOhost cloud platform because it just hangs and times out.

    This may be just a one off problem but as it is not obvious so may be affecting people who haven’t yet noticed.

    This is the actual post on which I discovered the problem http://bestfrenchmortgage.com/your-french-mortgage-and-the-credit-crisis/ and this is the shortcode that should reach it http://wp.me/p2NOUr-1iY but fails with a 404 the shortcode attempts to reach http://davidjromano.com/beta/your-french-mortgage-and-the-credit-crisis/

    Mert, any help or advice you can give me to fix this would be very much appreciates, best regards, David