I have just upgraded from Drupal-4.6.4 to Drupal-4.7-CVS (downloaded last night so the code should be about a day more mature than beta-3). Now I am getting a problem whereby users have to log in twice before they are granted access to the site. The first time they login, they are just re-shown the login box on the front page (no error messages are given to the user). They re-enter their login information and everything is fine. An error message is generated for the first, failed log in which reads:

Message: node/7 denied access.
User: Anonymous
Location : /intranet/node/7?destination=node%2F7
Referrer: /intranet/node/7

The site is being used as an intranet / groupware system and so it's setup to dissallow anonymous users from seeing any content. I'm using the front_page module to direct anonymous users to a "this site is only for registered users" message and to direct registered users to node/7 (a book page).

The site is running on Site5. They are using the following software versions:

Apache 1.3.34
PHP 4.4.1
MySQL 4.1.14-standard
Linux server running Kernel 2.6.9

This problem wasn't present when I was running Drupal-4.6.4

I have tried clearning the CACHE and SESSION tables but that didn't fix anything.

When users point their browser to www.mysite.com/intranet then they must log in twice. However, if they point their browser to www.mysite.com/intranet/node/7 then they only have to login once.

Perhaps this is actually a problem with the front_page module? (I'm using the latest version from CVS)

Many thanks,
Jack

Comments

dan_aka_jack’s picture

dan_aka_jack commented

Also, I should state that I am using clean URLs.

Zen’s picture

Zen commented

I'm not sure, but can you please disable the frontpage module and then test this again? Unless the issue is replicable, it's tough to do anything about these situations. If you can please also test this out with HEAD.

Thanks
-K

dan_aka_jack’s picture

dan_aka_jack commented

Hi,

I've tried disabling the front_page module and it does indeed fix the double-login problem. I'll try to download the most recent code soon.

Thanks,
Jack

chx’s picture

chx commented
Status: Active » Closed (won't fix)

this is a front_page related problem, then, so I set it to won't fix -- there is nothign to fix here.

dan_aka_jack’s picture

dan_aka_jack commented

OK... what's the best way of taking this issue to the front_page developers? Can I just change the "project" name by replying to this thread? Or should I copy-and-paste the description from this thread to a new front_page issue?

Many thanks,
Jack

chx’s picture

chx commented

yes, just change the project to front_page

dan_aka_jack’s picture

dan_aka_jack commented
Project: Drupal core » Front Page
Version: 4.7.0-beta3 » 4.7.x-1.x-dev
Component: user system » Code
Status: Closed (won't fix) » Active

Great, thanks. Done.

Dublin Drupaller’s picture

Dublin Drupaller commented

Quick questions.

Q. If you change the redirect for authenticated users to something other than node/7, what happens?

Q. Do you have any or did you have any *_access.modules installed in Drupal 4.6.4 or your new site ?

I just tried to recreate the same issue and wasn't able to.

Dub

Dublin Drupaller’s picture

Dublin Drupaller commented

Dan_jaka...can you enable your contact form ?

(go to MY ACCOUNT, click EDIT and enable your personal contact form).

Just tried to contact you about this.

I have tried everything to recreate the problem you're having but am unable to do so. The only thing I'm missing is what other modules you have installed...and what other modules you had installed with the 4.6.4 version that maybe affecting this.

Dub

dan_aka_jack’s picture

dan_aka_jack commented

I've enabled my personal contact form... I'll get back to you with answers to your other questions later today.

dan_aka_jack’s picture

dan_aka_jack commented

Q. If you change the redirect for authenticated users to something other than node/7, what happens?

I have just tried re-directing authenticated users to node/162. Very strangely, this has had no effect! If users point their browser to mysite.com/drupal then they have to log in twice and are then taken to node/7! I've searched my variable table for all rows containing the text "front_page" and here's the output:

front_page_text  	s:41:"This site requires users to be logged in.";
front_page_size 	s:6:"themed";
front_page_anon_redirect 	s:4:"node";
front_page_php 	i:0;
front_page_text_yes 	s:0:"";
front_page2_size 	s:8:"redirect";
front_page_redirect 	s:8:"node/162";
front_page_php_yes 	i:0;
front_page_breadcrumb 	s:1:"1";
front_page_breadcrumb_redirect 	s:6:"node/7";
site_frontpage 	s:10:"front_page";
form_id 	s:24:"front_page_settings_form";

No, as far as I remember I've never had any *_access.modules installed.

Thanks for all your help,
Jack

dan_aka_jack’s picture

dan_aka_jack commented

I've just tried emptying the cache table but that made no difference.

Dublin Drupaller’s picture

Dublin Drupaller commented
Status: Active » Closed (won't fix)

I have tried to recreate the same problem and am unable to do so..

Marking as wont fix as the error is most likely related to another module you have installed.

Dub

dan_aka_jack’s picture

dan_aka_jack commented

Hi there,

Hmm... I've just updated my site to the latest code from the CVS repository. I've also tried turning some modules on and off to try to find which modules cause the double login problem. As far as I can tell, it's only the front_page module that's both necessary and absolutely required to cause the double-login problem. I've tried turning on and off the node_privacy_byrole module but that didn't seem to fix the problem.

Jack.

npollock’s picture

npollock commented

I have the exact same problem. I am running a Linux FC4 server and ever since I upgraded to 4.7, the problem has haunted me. I just disabled every module except required and front_page and the same problem exists in FF and IE. I checked the httpd logs and the drupal logs, but no errors are logged. Also, I am on the latest cvs code as of tonight.

The first login displays the content of the node and the second login displays the menus.

Any help would be appreciated.

Norm

Dublin Drupaller’s picture

Dublin Drupaller commented

Just tried this again.

Unable to recreate the problem you are having guys. sorry.

Here's what I did:

(a) downloaded the latest version of Drupal 4.7 beta 5

(b) installed it as a clean, fresh, out of the box, install.

(c) downloaded the latest version of the front_page.module for Drupal 4.7.

(d) Installed it and it worked perfectly.

(e) tried switching cache on/off, clean urls on/off, installed other modules, closed browser window, used different browser, cleaned browser files cache and it still worked perfectly.

Here's a list of contributed modules I had installed:

1. front_page.module

Sorry I can't be of more use than that.

Dub

Dublin Drupaller’s picture

Dublin Drupaller commented

As a by the way...recommend you only use CVS module releases for CVS versions of Drupal and 4.7 module releases for Drupal 4.7. Ditto for 4.6, 4.5 module releases..only use them with the correct version of Drupal..

Am unable to recreate the error you're getting guys...can you point me to a link to your problem sites so I can have a look?

Drop me an email and give me a guest access login to see if I can work out why you're having the problem.

when posting link/emailing me..please indicate precisely which release of Drupal you are using (that can be found in the changelog.txt file in your root folder.

Cheers

Dub

PakWaan’s picture

PakWaan commented

I'm having the same problem with my site, running Drupal 4.7 beta 5. Users have to log in twice (and log out twice) in order for the command to be successful. I have a mostly-virgin 4.7 beta 5 site, and don't even have the front page module installed, so I don't think it's a front page issue.

I can email you a user name and password if you want to check it out - you can contact me through my contact page.

dan_aka_jack’s picture

dan_aka_jack commented

Hi,

I believe there are two separate issues here which both cause very similar problems.

I'm as sure as I can be that, on one of my installations, the frontpage module does produce double-login problems. The "frontpage double login problem" has some specific qualities: in particular, every user ALWAYS has to log in TWICE.

A separate problem is a multiple-login problem that is independent of frontpage module as described here This problem is intermittent and sometimes requires users to log in up to four times before access is granted.

Perhaps the two issues are related but, none the less, I believe there are two issues here that we mustn't merge into one.

reggie75’s picture

reggie75 commented

i set cookie lifetime to 0 (in sites/default/settings.php) so no cookie gets created on disk.

///ini_set('session.cookie_lifetime', 2000000);
ini_set('session.cookie_lifetime', 0);

this seems to have solved it for me.

the only drawback is when the user closes his browser, starts it again and comes back to the site, he is not logged in. (can pass it off as a feature :))

PS: You need to DELETE the OLD COOKIES after you do this, else it never lets you log in.
(in IE: Tools > Internet Options > Delete Cookies)
(in FF: Tools > Privacy > Cookies > Clear Cookies)

worked like a charm after that.

PPS: I also added the following line in settings.php,
but i dont think it would make any difference
ini_set('session.cookie_domain', '.domain.com');

where "domain" is your domain name.

Thanks,
Rajesh

MichaelCole’s picture

MichaelCole commented
Status: Closed (won't fix) » Active

This is still a problem. Disable-in front_page fixes this for me as well.

I can offer up a zip backup of SQL and Web files if anyone is interested.

Dublin Drupaller’s picture

Dublin Drupaller commented
Assigned: Unassigned » Dublin Drupaller
Status: Active » Closed (fixed)

Hi Michael,

Disabling the front page module doesn't solve the problem...it worked once for me when I managed to recreate the problem and disabled the front page module, but, after that, the double login problem comes back.

I'm afraid the front_page.module doesn't control logins....have a look at the following double login issue:

http://drupal.org/node/87372

That might help.

Dub