Brand new blank sites install WordPress fine, but the normal app/sql/ folder is missing (app/public is present). Where is the database for WordPress being installed??
Steps to reproduce
Click the plus button to make a new blank site. Whether using the default or custom config it happens. I’m surprised nobody has reported this yet.
Environment Info
Describe your environment.
What Operating System are you using? Windows 11
What versions of site software (Nginx, Apache, PHP, MySQL) is used? Tried both, but latest try is Apache 2.4
What version of Local is installed? Version 9.1.1+6738
Supporting info
Please provide your Local Log. See this Community Forum post for instructions on how to do so:
That didn’t fix it. I’m having it happen on 2 different Windows computers when creating brand new clean WordPress sites even. One laptop has Windows 10 and the other Windows 11.
Maybe this is a problem in Windows only?
Created a brand new site today as a test - same issue.
I updated LocalWP version on the Win 10 laptop to: Version 9.1.1+6738
In a nutshell, the the SQL folder was created correctly in sites before November, but not after November.
As far as I know this has always been the default behavior of Local. When you first create a site, no SQL file appears until the first time the site is stopped.
I’ll check with the team on this just for clarification around the “why”. I do agree that’s not the most intuitive and if it must remain this way it might be a good idea for us to call it out in some more clear documentation somewhere.
The sql folder is only created if you click the “Stop site” button – It does NOT create the folder if you simply close the LocalWP application.
That’s correct. MySQL needs time to dump the SQL file. When you quit Local it sends a termination signal, and we cannot guarantee that we can artificially keep Local and all of its child processes open long enough after the termination signal for SQL dumps to succeed.
If creating SQL dumps on quit is critical to your workflow, it’s worth stopping sites before quitting Local. I agree with @Nick-B that we could better document how this currently works.
