Chris A. a11n

Are you able to visit Options -> Permalinks and save your permalink structure.

The permalink option should match that of the site you exported.

Please let me know if that helps at all.

For example, if I choose to pull just the comments table into the dev site what about happen if my dev site doesn’t have the required postmeta data from the live site?

You’ll likely have display issues / errors if your themes or plugins attempt to access commentmeta that doesn’t exist.

Hi, with WP Migrate DB the old tables are completely dropped and replaced by the new ones. No merging takes place at any time.

Hope this answers your question.

I’ve discussed this with the team and unfortunately this configuration is not currently supported by the plugin.

Are you able to mimic the folder structure you have on your live site for your local site?

i.e. have your local site run WordPress from a /wordpress/ directory?

Thanks for this report. I’ll have something for you soon!

This has been corrected in an upcoming version of the plugin. Creating the wp-content/uploads folder manually should do the trick in the meantime.

Tyler, this has been corrected in the next release of the plugin.

Stay tuned for that release, sorry for the inconvenience.

Currently the only solution is to temporarily disable WP Session Manager before attempting to run the export.

We’re looking into fixing this in an upcoming release.

This is a bug in the current release of the plugin but has been fixed in our development version.

This should be fixed in the next release of the plugin.

Apologies for the inconvenience, hang tight!

WP Migrate DB currently does not support WordPress multisite installations.

You’ll need WP Migrate DB Pro for that, you can read more on the official WP Migrate DB Pro website.

Feel free to email these download links to [email protected].

As for the issue, are you able to temporarily disable your active plugins (except WP Migrate DB of course) and attempt to run another export?

I just want to ensure that the problem is not being caused by a plugin conflict.

Currently the plugin will export and process the DB until it’s done.

You could possibly check if something has gone wrong by examining the DB dump file while it’s being written to on the file system. If at any time the file size stops increasing, it’s likely that a problem occurred.

You might also want to check that it’s not stuck in a loop and rewriting the same data over and over again to the dump file (unlikely).

It’s not outside the realm of possibly that a migration would take over an hour but it’s extremely unlikely.

You can stop the migration at any time by simply refreshing the page, it won’t break anything important, only the dump file.

We’re currently in the process of overhauling the plugin a little to provide more detailed migration progress and better error handling.

Hey Guys,

I work with Brad on WP Migrate DB and thought I’d chime in here to try to figure out what might be happening.

Brad has provided me with a few of the dumps that you guys have provided for testing purposes. This is what I’ve tried so far:

1. Import the original dumps into my local environment
2. Get the website running (by changing admin password / home & site urls / etc )
3. Dump the website data via phpMyAdmin ( i.e. dump-1 )
4. Dump the website data via WPMDB
5. Import the WPMDB dump into the same installation
6. Dump the website data via phpMyAdmin ( i.e. dump-2 )

I then ran a diff tool across the phpMyAdmin dumps dump-1 and dump-2. Unfortunately they appear to be identical. So WPMDB appears to be doing it’s job in that the data is exactly the same before and after the import.

It sounds like you guys are seeing odd characters in the dumps but is this actually affecting the content at all? That is, are you seeing weird characters on the front end of the website when you import the WPMDB dumps?

Same problem ??

If the plugin was not installed from the “beginning of the blog” then it has not possible way of determining the number of hits a particular post has had.

It can’t figure out the clicks retroactively, it’s simply impossible.