Local Community

WPE Backup Zip Fails to import

Support
#1

Multiple attempts at this failed. I’ll try working around it now. I just generated a FULL backup on WPE, and dragged the zip onto local. Tried multiple configs, but last time used “preferred” settings on Local 6.7 (just updated). And the import fails saying that it’s not a supported zip.

Two screenshots, the first shows the first password prompt. Immediately after entering that it fails and then pops up the second prompt for a password.

CleanShot 2023-03-27 at 14.15.23
CleanShot 2023-03-27 at 14.15.231920×1009 130 KB

CleanShot 2023-03-27 at 14.15.34
CleanShot 2023-03-27 at 14.15.341920×1006 127 KB

Note, importing a different site from WPE as a test succeeded.

Whatever is in the logs (in the screenshot) is insufficient to know why this may have failed.

#2

Hi @jb510

Sometimes we see this with WP Migrate when ALL files are included like Other for example. All Local really needs for an import is wp-content and SQL, if the full site export includes full backups of the site, database, or even bloated media directories if the site is super large this could all cause a conflict.

If you’re able to trim the export down to just the essentials, then you should be able to import it. If you need to try something more manual, you could go through steps like these:

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
  • If that works, now Search and replace the domains. wp search-replace ’ https://production.com ’ ‘http:mylocalsite.local’

Keep us posted if you still have any trouble!

#3

FWIW, that’s essentially what I did for a workaround (still imported full DB). Just a weird repeatable bug though.

FWIW2, I usually see these problems with tables from SearchWP. Seems like there is a collation glitch that can happen there. But I’ve seen it with a few others similarly large “log” style tables…

#4

@jb510

Thank you for your insight! We’ve definitely seen this come up and it isn’t always the same culprit. So your information is helpful. I’ll relay this to our Dev teams for both Local and WP Migrate. If you think of anything else that might be beneficial let us know!