Unbeknownst to me, Local by Flywheel became an entirely new, separate app just called Local. I missed that, so apparently I’ve been using the old version even though a new one was out.
Now I’ve upgraded macOS to Big Sur, and the old Local by Flywheel no longer works. I was working on a local site up through Friday 11/14, but the most recent backups available in my app/sql/ folder are from 11/11—and I can’t get them to import into new database in Local anyway.
So I guess what I’m wondering if the “raw” MySQL database exists in some system folder somewhere so that I could access it and extract the work I did between 11/11 and 11/14.
I can create the new WP install with the same name, copy all the files from old ‘local by flywheel’ app. But how do I copy the old database to the new local app?
I can create the tables with the schema files. But importing the rest doesn’t really work.
You must export the site from Local 3.x and import it into Local 5.x. This has nothing to do with Big Sur and everything to do with transitioning from Local 3.x to 5.x.
Hey @nickfindley, Big Sur did break Virtual Box which is what Local Classic used to manage the WordPress sites.
If the SQL files don’t have the correct content, then it’s likely that this content is lost since the raw database files for Local Classic exist within the Virtual Machine.
You might try using the files for the site by following the steps outlined in the “Restoring From Only Local Site files” section of this help doc:
I have just installed the latest VirtualBox 6.1.16 r140961, and Local by Flywheel works fine with it.
If during the installation of VB you get an authorization problem about an Oracle extensione, follow these instructions.
Cheers,
Guido