Users need to login 2 times in order to login

if this is a particular firefox issue check for the site, i remember such an issue was being discussed. but is this valid for all browser types?

are you using the latest 4.7 version of the module, or the latest HEAD version? is your drupal core version the latest 4.7 version? please make sure you have updated to the latest 4.7 versions for both, then report back if the problem persists.

does it switch between delhilive.com and www.delhilive.com when you try to login?

there is a setting in .htaccess

this section:

# If your site can be accessed both with and without the prefix www.
# you can use one of the following settings to force user to use only one option:
#
# If you want the site to be accessed WITH the www. only, adapt and uncomment the following:
# RewriteCond %{HTTP_HOST} !^www\.example\.com$ [NC]
# RewriteRule .* http://www.example.com/ [L,R=301]
#
# If you want the site to be accessed only WITHOUT the www. , adapt and uncomment the following:
# RewriteCond %{HTTP_HOST} !^example\.org$ [NC]
# RewriteRule .* http://example.org/ [L,R=301]

they get redirected

Using the method in .htaccess is not a good way to fix this problem. I changed my .htaccess as instructed and found that I could not access other sections of the site that are not part of drupal. ie; www.example.com/sample versus sample.example.com. When I set to only use www.example.com, then sample.example.com does not show up. Same thing happens when I remove the www from the front.

So, I'm having to use neither described method. And when a user logs in, it seems that nothing happens. No change in status of log in. However, if the user then goes to another page right after the initial log in, then they are actually logged in because the user status shows they are logged in. The remainder of the session works as normal. It's just when they initially log in.

This seems to me to definitely be a bug. Is there no way to fix this without having to modify the .htaccess file?

Okay, the rewrite rules in jbrown's .htaccess assumed, as the comments say, that you wanted:
# [...] to force user to use only one option

and that
# [...] you want the site to be accessed WITH the www. only

It redirects ALL hostnames other than www.example.com to www.example.com. Which is normally what one wants, since it also catches the case where someone accesses the site by ip-address, which would trigger the 2nd-login behavior as well.

But in your situation, you apparently have other valid "subdomains" parked on the same IP address as www.example.com and you don't want to redirect those, ONLY http://example.com/* to http://www.example.com/*

So try this:

RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
RewriteRule (.*) http://www.example.com/$1 [L,R=301]

hth,

-dave

David, your .htaccess code worked great. Thank you!

RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
RewriteRule (.*) http://www.example.com/$1 [L,R=301]

this is not a logintoboggan issue.

@manuj_78: try using drupal's standard login block, and see if you can replicate the issue. for the most part, logintoboggan uses the core login block's functionality, especially for standard logins--so i'd be surprised if the problem you're experiencing is related to logintoboggan. this sounds more like an issue with your site's setup, or with drupal core.

no, they will not. the login block on access denied is a logintoboggan function. i'm merely suggesting that you more closely investigate the source of the problem by trying to replicate it with logintoboggan disabled. if you can do this, then the issue is not an issue with logintoboggan most likely.

Okay, I tested to see if I would have the same results with the standard drupal login versus the logintoboggan module and I could not reproduce the error of having to login and not be shown that you are actually logged in until you go to another page/node. So this is definitely a logintoboggan bug! I have even done the .htaccess modifications, and even though I thought this had fixed the problem, it actually did not fix the problem. Note that I am running the latest 4.7.3 drupal and the latest logintobogin module.

setting back to a logintoboggan issue. since i have never seen this problem, or been able to reproduce it, i'm going to leave this issue for somebody else to confirm/address.

creatorsdream, when you login the first time, does the URL change to append a ?time=1160696070? That's the standard way for Drupal to force the browser to NOT use a cached version.

Also, what browser(s) have you used that exhibit this problem? Please specify name and version (example: Opera 8.0)

JohnAlbin, I'm sorry I haven't replied sooner. Actually, I can't really give you any good information because I ended up moving my web site over to site5.com. The error has gone away since the move. I can only determine that the reason for the error is due to either php or mysql versions. My site5.com versions which work with logintobaggan are:
PHP version PHP/4.4.4
MySQL version 5.0.24-standard

The old server where the problem was found uses MySQL 3.23.58-Max-log and PHP Version 4.3.11

Hope this helps.

Without any more details, cannot fix.