Export / Import from WP Migrate - Blocking, Wrong Message

Support
,
1

Bug Summary

When attempting to import a zip file exported with WP Migrate (v2.6.8) through Local (v7.1.2+6410), I receive an error message about the file’s compatibility, even though I’m using the plugin suggested by Local’s guide.

Steps to reproduce

  1. Export data from a WordPress site using WP Migrate (v2.6.8), producing an 80MB zip file.
  2. Attempt to import the zip file into Local (v7.1.2+6410).
  3. Wait for the progress to reach 100%.
  4. Receive an error message indicating the zip file’s incompatibility.

Environment Info

  • Operating System: [PC specifications, e.g., Windows 10, 8GB RAM, etc.]
  • Site Software: Custom - PHP Version 7.3, Apache 2.4.43, MySQL 5.7.28.
  • Local Version: 7.1.2+6410

Supporting info

Local Log Entries:

  • “Access denied for user ‘root’@‘localhost’ (using password: YES)”
  • “Access denied for user ‘unw9qjoqyrwou’@‘localhost’ (using password: YES)”
  • “Error: ERROR 1146 (42S02) at line 1: Table ‘local.oak_yoast_seo_links’ doesn’t exist”
  • “Unable to import C:/Users/{username}/Local Sites/superinformaticom/app/sql/database.sql”
  • “Unable to import site.”

I tried a new export attempt adding the “WordPress Core Files” and “Compatible with older versions of MySQL (pre-5.5)”, but to no avail.

The error also indicates login attempts to the database with the usernames ‘root’ and ‘unw9qjoqyrwou’.

2

The error message provided seems to be misleading (I suspect it is a bug itself). The actual issue appears to be with the database import process. I’m also wondering if the error could be stemming from a discrepancy in the table prefixes. The $table_prefix for the migrating site is 'oak_

3

Hi @Gik25

Sometimes there can be things in the migration file that confuse Local. Things like site backups, DB copies, etc. Something you can try and do is unzip the file and break it down into just the WP Content and SQL and then zip those back up and try again. If it still errors out then there might be an issue with the database.

You could attempt a more manual import. The steps would look like this:

  • Unzip the file in a common location, like the desktop
  • Create a new, blank site in Local. Use whatever username/password you like since you’ll overwrite the DB with this site archive’s dump.
  • Copy the wp-content folder from the unzipped location to this newly created site’s location
  • Copy the correct SQL dump to the site root.
  • Within Local, open the site shell
  • Import the dump with wp db import <dumpfile>
  • If that works, now Search and replace the domains. wp search-replace ' https://production.com ' 'http:mylocalsite.local'