vBulletin Version = 5.1.0
PHP Version = 5.3.5
MySQL Version = 5.1.54
Any Addons installed = vbShout
Does the issue occur in a default style? = Yes
Error message on the screen' = none
Browser and Browser version used. = Have used both IE and Chrome and see same issue
Problem Description:
Cookies do not seem to be found once a session is closed even though the "Remember Me" checkbox is checked. Session timeout is set at 15 minutes. Once this has expired, the user is logged out and will always have to login again. I checked the cookies on a local machine and can see that the password cookie is being stored on the local machine and is set for 30 days expiration date. I also checked that both config.php files have the same prefix for the cookies. Other cookie variables are set at their default values in the AdminCP. I have tried both using the .domain.com entry and the www.domain.com entry and see the same behavior.
The issue seems to have popped up since upgrading from 5.0.5 to 5.1.0 although I don't have hard evidence showing this. But since the upgrade I have had several users complain about it and didn't have this prior.
Thanks for any help or guidance.
PHP Version = 5.3.5
MySQL Version = 5.1.54
Any Addons installed = vbShout
Does the issue occur in a default style? = Yes
Error message on the screen' = none
Browser and Browser version used. = Have used both IE and Chrome and see same issue
Problem Description:
Cookies do not seem to be found once a session is closed even though the "Remember Me" checkbox is checked. Session timeout is set at 15 minutes. Once this has expired, the user is logged out and will always have to login again. I checked the cookies on a local machine and can see that the password cookie is being stored on the local machine and is set for 30 days expiration date. I also checked that both config.php files have the same prefix for the cookies. Other cookie variables are set at their default values in the AdminCP. I have tried both using the .domain.com entry and the www.domain.com entry and see the same behavior.
The issue seems to have popped up since upgrading from 5.0.5 to 5.1.0 although I don't have hard evidence showing this. But since the upgrade I have had several users complain about it and didn't have this prior.
Thanks for any help or guidance.
Comment