Closed (fixed)
Project:
Persistent Login
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Minor
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
8 Dec 2008 at 19:25 UTC
Updated:
15 May 2009 at 08:40 UTC
D6.6 I have installed mod, changed cookie lifetime to 0 in settings php, and ran updates. The database is showing the 2 tables, remember me check box is displayed, warnings in profiles are showing up. But the site is not remembering the user. Is there a trick to this or some added documentation?
thank you,
dave
Comments
Comment #1
vikramy commentedHi Dave,
Are you still having problems with this module?
Comment #2
dbeall commentedI never could get it to work as expected and switched to the remember_me6.x-2.0. I was kinda bummed because I like the way persistent login works after reading the differences between remember me and persistent login.
I wish i could give you more info, but i am not a php programmer which makes trouble shooting difficult. I am very willing to help test on my live site, I can put it back in if you want to try it..just a thought..
thank you for your time and work !
dave
Comment #3
vikramy commentedWell, I can try. But I also noticed some problem with this module.
Check this.
http://drupal.org/node/357166
Comment #4
dbeall commentedI was thinking about letting the module mature while the php gods do their magic.
Comment #5
vikramy commentedThats true.
Comment #6
markus_petrux commentedI guess title now reflects the original issue.
Maybe some kind of conflict with another module?
a) Please, visit Administration -> Site configuration -> Performance. There should be a message in red that lists modules incompatible with aggressive mode caching. Aside from PL, what else?
b) Using any other module hooking into the login/session management such as Login Toboggan or some other kind of user integration with 3rd party backend?
Comment #7
markus_petrux commentedComment #8
markus_petrux commentedCould this issue be related to: #445804: Logins not peristing anymore after upgrade to beta5 ?
Maybe you can try with Beta6 and see if the problem is solved?
If not, then please read #6, as it might be related to something else on the installation that conflicts with PL.
Comment #9
markus_petrux commentedThe code in 6.x-1.x has been changed a lot sine this bug was reported. So, let me assume this is fixed. Please, feel free to open a separate issue or re-open this one if the problem persists in your case. Thanks