Hello.

After upgrading my D5 to D6.latest, and upgrading LoginToBoggan to 6-1.6 , I experienced the following problem:

With CACHE enabled (Normal) , and "Immediate Login" checked, when one user registered, he was connected to the previous registered user's account. The problem resolves when CACHE is Disabled or by unchecking "Immediate Login".

Please review this as I made some other minor changes to my settings, although I seriously doubt it is something different.

Comments

hunmonk’s picture

hunmonk commented
Status: Needs review » Postponed (maintainer needs more info)

i need you to give me exact steps to reproduce -- if you are not able to reproduce this problem consistently, and tell me how to do the same, then i can't address it.

gkatsanos’s picture

gkatsanos commented

I will give it a shot, even though given the complexity and the interaction of different modules, and maybe some fault in the upgrade process, I don't guarantee it.

Have CACHE in /performance/ always set as Enabled (Normal).

Get a D5.latest, install Logintoboggan, check "Immediate Login".

Upgrade to D6.latest, upgrade LogintoBoggan.

Register as a new user.

In my case, immediately after, I am connected in the account of the previous user registered.

hunmonk’s picture

hunmonk commented

I will give it a shot, even though given the complexity and the interaction of different modules, and maybe some fault in the upgrade process, I don't guarantee it.

see, this right here is a big red flag for me.

please start with a *clean* drupal installation, and enable only core modules and the logintoboggan module. if you cannot reproduce the problem there, then you can be pretty sure the issue is coming from another module, or an upgrade problem. if that's the case, then start enabling the other modules and see if the problem appears.

report back with your findings, and we'll go from there.

gkatsanos’s picture

gkatsanos commented

I am sorry but I don't have the resources (the time mostly) to do this. My contribution at the moment is limited in informing you of the problem I faced. I hope someone else can take it from here.
Also, if it is upgrade problem, it doesn't mean that it's "someone else's" fault. What if the issue hides in the module's upgrade procedure?

hunmonk’s picture

hunmonk commented

I am sorry but I don't have the resources (the time mostly) to do this. My contribution at the moment is limited in informing you of the problem I faced. I hope someone else can take it from here.

that someone will not be me i'm afraid... ;)

i can't waste my support time chasing down people's database and module dependency issues. you have to meet me halfway and triangulate the problem to LT specifically.

Also, if it is upgrade problem, it doesn't mean that it's "someone else's" fault. What if the issue hides in the module's upgrade procedure?

i clearly said in my previous post "report back with your findings, and we'll go from there" that doesn't rule out a problem in the upgrade path for LT. i'm starting with disabling the other modules because that's most often it's a dependency problem. it's your installation, with your set of other installed contrib modules -- so it's your responsibility to take this next step... :)

gkatsanos’s picture

gkatsanos commented

I will do a local copy of my website within the weekend for other testing purposes too, and I'll try to reproduce the problem with disabling all other contrib modules.
(I hope there isn't an issue with my server's caching)

carlwohlforth’s picture

carlwohlforth commented

I'm seeing something like this. I started with Drupal 6.13. I will try to reproduce with minimal setup and will report back if I am able to reproduce.

carlwohlforth’s picture

carlwohlforth commented

While trying to get a repeatable test case I did duplicate this problem. I was logging in as different users then logging out. Eventually some buttons lost their formatting and the block which lists logged in users showed a user who had been logged out. Once I logged in as one user but ended up being logged in as a different user.

Since I am unable to come up with a repeatable test case I can't provide more information.

Since normal expected use of our website is for each user to have their own computer this issue is not critical for us. We don't expect them to repeatedly log in and out or to create several accounts.

hunmonk’s picture

hunmonk commented
Component: Miscellaneous » Code

i'm not able to reproduce any issues w/ the 6.x-dev code of drupal core and 6.x-1.x-dev of LT, using the settings detailed in #2. i don't have time to try it via an upgrade from 5.x.

so again, if someone can find a way to reliably reproduce this issue on a clean install, i'll look at it.

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

The behaviour described in #8 seems to have nothing to do with "immediate login" being set. If #8 is/was an issue, I don't see how LT could be anything to do with it, because core login/logout routines are always used. I have just checked any code touching the login/logout process, and this only happens in two places, as far as I can tell:

1. When the user can login with an email address there is a validation hook, but this is totally harmless.

2. When "immediate login" is enabled then there is a custom login function, but it looks perfectly safe and anyway, is out of play after the initial user login.

So anything that comes from logging in and out many times is almost certainly not an LT bug. It's possible you found a core problem that can be reproduced by hammering login and logout from the same browser repeatedly. It's also possible this was down to a browser/session/cookie handling bug.

Anyway, to cut a long post short - since no one ever actually reported back on this and it's over a year old AND it's unlikely to be related to LT anyway, I'm going to close this. It's not nice to have 'critical' issues hanging around - especially when they're probably non-issues. =)

If someone can provide reproducible steps to repeat this bug in Drupal 6 or Drupal 7, we're all ears - re-open.