Log in with log in block requires users to log in twice
Liam McDermott - January 10, 2008 - 07:51
| Project: | Boost |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Occassionally am finding users have to log in twice, am using LAMP (PHP version 4, Apache 2). Here are the steps to reproduce:
- enable login block, display it on every page;
- clear all cookies;
- load a cached page;
- log in using login block on cached page;
- log in will silently fail, cached page will reload;
- attempt to log in again, this will work;
I checked, the DRUPAL_UID and SESS[...] are present after the first login attempt, and it's not the cached version of the page which is served subsequent to the first log in attempt.
#1
One more thing: a 'Session opened for ..user..' log entry is created for the failed login attempt.
#2
I have the same issues, with the log entry and everything. Will turning off cached pages temporarily resolve this? I would like to keep the cached pages on because some of my users are in rural areas. Most of the users aren't tech savvy and logging in again or refreshing the page probably won't occur to them.
#3
eh? :)
#4
fozilla: The workaround I used was to switch off the login block and put a 'login' link in the main menu of my site, pointing people to /user People seem alright with this. :)
#5
i wonder if the browser is serving the cached version of the home page after logging in with the block?
try a ctrl-f5 (force refresh) after the first login and see if you are magically logged in now.
i've found some other issues with the browser serving cached pages after login/logout when it shouldn't - it's only noticeable if you've got content on the page that changes for logged in vs. anon uses (like the login block)