- Issue created by @narbehm
- Status changed to Postponed: needs info
2 months ago 5:16am 16 August 2024 - 🇨🇭Switzerland saschaeggi Zurich
Did you check the logs for PHP errors and the developer console in the browser for any site specific JS errors?
I can't think of how Gin Login would be involved in any form here.
Does it work if you deinstall Gin Login?
My apologies. After uninstalling Gin Login, the issue still persists. It must be related to core or perhaps another module. I will do more investigating to see where the issue is. The logs just show and unsuccessful login. If I change the username to a.b@c. it works. It's only when I have a username of x.x@x.x where it stops working. Perhaps the authentication logic in core is recognizing this as an email and attempting to find a user with that email even though it's a username.
In any case, these users were able to authenticate with no in D 10.2.7 and not cannot after updating core to 10.3.2 along with all used modules.
You can close this issue and sorry for the mistake.
- Status changed to Closed: cannot reproduce
2 months ago 5:48am 16 August 2024 - 🇨🇭Switzerland saschaeggi Zurich
Alright will close this issue. A good place to start might be to have a look at Core's issue queue for any known issues.
Cheers!