• Handoko

    (@handoko-zhang)


    Great plugin, it’s really useful.

    Unfortunately, it won’t correctly migrate to the site if they have different table name prefix. The default WordPress table name prefix is “wp_“, but for some reason, the destination may use different prefix.

    A peek on the result database, I can see the tables have successfully copied, but using the original prefix name.

    Hope it will be solved on next release.

    http://wordpress.org/extend/plugins/wordpress-move/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Related to this, beware if you’re moving from a dev server to a server with a database that hosts several domains… Imports the tables strictly as is, so if you hadn’t thought that through (like I hadn’t :)), you’ll overwrite the wp_ prefix tables when you didn’t intend to.

    Would be nice to have an option to set a new DB table prefix, at the same place you can set the new domain.

    I initially thought it was unnecessary (hence such an option is not available currently) but I now see the unavailability of it renders the plugin useless under some circumstances.

    I promise I will ship this feature with the next release 🙂

    Hey, thanks for the quick response :).

    The plugin worked great otherwise, by the way; really really useful. Thanks!

    It’s always nice to see people using and appreciating my work 🙂

    @mert – Great plugin except for the prefix problem. Unfortunately, this is a showstopper for us. We never use the standard prefix for security reasons.

    Any idea when this will be fixed?

    I hear ya!

    I have an exam to take and a couple of papers to turn in, so it may take about 2 weeks. I love coding more than the school work, so probably way earlier than that 🙂

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Plugin: WordPress Move] Fail to migrate if using different table prefix’ is closed to new replies.