-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session::regenerateSessionId may cause warnings #9496
Labels
Comments
@kinglozzer your changes are in the 4.5.3 tag (https://github.com/silverstripe/silverstripe-framework/blob/4.5.3/src/Control/Session.php) - so I guess it means there's still an edge case to be dealt with? |
Yeah I think I fixed one trigger for this bug, but not the root cause |
lekoala
added a commit
to lekoala/silverstripe-framework
that referenced
this issue
Apr 27, 2020
PR merged so this can be closed :D |
lekoala
added a commit
to lekoala/silverstripe-framework
that referenced
this issue
Mar 31, 2021
Backport this change to SS3 silverstripe#9496 Recently got the issue on a old project
lekoala
added a commit
to lekoala/silverstripe-framework
that referenced
this issue
Mar 31, 2021
Backport this change to SS3 silverstripe#9496 Recently got the issue on a old project
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected Version
4.5.3
Description
Recently found this in my logs in production:
error-log.WARNING: E_WARNING: session_regenerate_id(): Cannot regenerate session id - session is not active {"code":2,"message":"session_regenerate_id(): Cannot regenerate session id - session is not active","file":".../vendor/silverstripe/framework/src/Control/Session.php","line":652}
This happens when sending password reset links
Steps to Reproduce
Get a password reset link, open an incognito window, paste the reset link (in my case, it's hidden by a tracking link from the mail api, so it triggers a redirect) : you get the warning
It may well be due to the incognito window freshly opened or the redirection from the mail api. In any case, it shouldn't happen
Possible ways to solve it:
The text was updated successfully, but these errors were encountered: