Importing site includes unwanted SQL files

Bugs
1

Bug Summary

I ran into the issue with MariaDB trying to update itself to an older version and it prevented a few sites from starting. @Nick-B provided advice to delete and reimport the site ( Missing MariaDB - #7 by Nick-B ). This worked great for the first site, but on the second site I imported, there was an additional SQL file being imported that wasn’t wanted.

I zipped the old site directory including the app, conf, and logs subdirectories – the app/sql/local.sql file was recent. The site import process extracted everything, and then imported an older backup SQL file from WP Migrate (app/public/wp-content/uploads/wp-migrate-db/[sitename]-backup-[timestamp]-gzezn.sql). After that, it imported the correct SQL file.

It is unexpected for the site import process to pull SQL files from other directories beyond the app/sql directory. If it’s being done for a particular reason, perhaps the user should be given the opportunity to reject additional SQL files if the expected file (app/sql/local.sql) is available. I know that older versions of Local stored SQL files elsewhere, so this might be a historical artifact.

Steps to reproduce

  1. Run a WP Migrate database backup on a site.
  2. Create a ZIP file from the site directory that includes that that database dump file.
  3. Import that ZIP file to a new site and see both the backup and default SQL files imported during the process.

Environment Info

Describe your environment.

  • What Operating System are you using? Windows 11
  • What versions of site software (Nginx, Apache, PHP, MySQL) is used? Not relevant here
  • What version of Local is installed? Version 10.1.1+6939

Supporting info

Please provide your Local Log. See this Community Forum post for instructions on how to do so:

Include any screenshots or video recordings of the issue to help others reproduce.

3

Thank you for raising this @burt! I’ve reached out to the Devs and created a ticket for our backlog to dig into this behavior further.