For those having this issue. I noticed that on Windows 11 with the latest update, when creating new sites, local is adding the Authentication keys and salts codes at the bottom of the wp-config.php file.
These should be loaded usually in line 53 right after this:
/**#@+
* Authentication unique keys and salts.
*
* Change these to different unique phrases! You can generate these using
* the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}.
*
* You can change these at any point in time to invalidate all existing cookies.
* This will force all users to have to log in again.
*
* @since 2.6.0
*/
HERE!!!!
define('AUTH_KEY...
...
/**#@-*/
To fix, just copy the lines 96-103 to line 53, or from the line where you see:
define('AUTH_KEY
Until the last one of the define scripts.
I hope this helps to anyone else having this issue.
I’d rather not mess with php files.
Local was meant to make it easier. Until We hear that Local works with Windows again, we’ll just work on hosted deployments.
Hi all - This issue has been addressed in the latest release of Local, currently in Beta - Local Beta 7.0.2
If anyone is able to download the Beta release and confirm the issue has been resolved, that would be great. Everything has looked good in our QA process, but always good to double check.
We’ll put this on the fast track to a stable release tomorrow morning!