-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Increase session timout #1050
Comments
There's really no simple way to set a session timeout to 'forever' because the the session cookie needs to take a unix timestamp (date in seconds). The only real option is to make that number bigger. We can look at increasing this available option in the admin, but in the meantime you can edit the value directly in |
Actually the timeout has no maximum even in the admin:
Where are you seeing a maximum? |
Interesting. I tried that with 9999999999999 and got 'Expiry date cannot have a year greater than 9999' when visiting the normal website (not the admin interface). I created this issue, because 9999 was to little for me. Using 99999999 works. |
Ok that probably goes beyond the limit of what a computer can handle for dates. |
I propose changing the error message from |
The error message is coming from php saying the year cannot be larger than 9999. I.e. With your 9999999999999 value the calculated expiry date is larger than 12/31/9999 which is beyond a valid date. |
BTW, added a quick fix to ensure that you don't go beyond the max value. |
Great, thanks! :-) |
I think, one can sett the session timeout in
system/config/system.yaml
to a maximum of 9999.I would like to increase that to weeks or "forever".
The text was updated successfully, but these errors were encountered: