Closed (fixed)
Project:
Persistent Login
Version:
4.7.x-1.0
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Dec 2006 at 15:36 UTC
Updated:
18 Jan 2007 at 20:24 UTC
I am using drupal 4.7.4 with cache enabled.
I found that the persistent login does not work properly.
The users see that they are logged out if they close the current browser and re-launch the browser.
Wasn't there this kind of reports before?
Thanks very much.
Comments
Comment #1
bjaspan commentedThere were problems with caching before, but I fixed them. What is your site?
Comment #2
ksoonson commentedmy site is http://kldp.org
if you need more information, please let me know.
Thanks very much.
Comment #3
bjaspan commentedI visisted the site, registered for an account, logged in with Remember Me checked, closed the browser, and re-visited the site. A new Persistent Login cookie was issued (correctly) and the site displayed "Welcome back, bjaspan."
I don't see a problem.
Comment #4
ksoonson commentedHi, thank you very much for testing the site. I don't think you can read Korean. :-)
But if you can try automatic translation from Korean to English, then http://kldp.org/node/76223 will let you know that all these people who posted reply are having problem with persistent login.
Thanks again very much.
Comment #5
bjaspan commentedI tried Google's automatic translation on that page but got nothing useful. If Persistent Login is not working on your site, I am going to need a test case.
Comment #6
ksoonson commentedThe staff admin of my site has found workaround.
I was using the persistent login with expiration time set to '0' so that it does not expire.
But it seems like the cron job(http://yoursite.com/cron.php) of drupal core seems to affect this value in the database.
I set the value from '0' to '30' and it works fine now.
I don't know which one is responsible for this but it seems like either the module or the cron.php needs to be fixed.
Thanks
Comment #7
bjaspan commentedIndeed, PL's cron hook was erasing PL sessions when the maximum lifetime was 0 (unlimited). Ooops.
Fixed in the development snapshot for 4.7 and 5.
Comment #8
bjaspan commented