I just created my vanilla forum a week ago. I have about 60 users registered. I'm starting to notice that it takes two login attempts before I'm authenticated. What are some tips to troubleshoot the root cause of this behavior? Has anyone else seen this behavior?
I've seen this happen before. Make sure that your FORWARD_VALIDATED_USER_URL configuration setting exists and points to your discussions index.
If you sign in and it puts you back to the sign in page, try to manually change the url to point at your discussions index to see if you are actually successfully signed in. If you are, then it is definitely a redirecting error and probably has something to do with that FORWARD_VALIDATED_USER_URL setting.
This is also on the address line when I first access the site. So I am not sure - is there something wrong with the address line? I think that I have configured Vanilla correctly. I notice that the Lussumo Community address when signing in doesn't have the 'SignOutNow" part - but I don't know why it puts that there on my installation.
I cannot find a file named 'config' in the entire directory structure. However, in the file 'settings.php' under the 'appg' directory, it has a line that reads:
It is still a problem for my site, and I have determined that it is affecting users who are accessing with Mozilla Firefox. Under IE it is not a problem.
Turns out the comment I posted on http://lussumo.com/community/discussion/7087/internet-explorer-60-forum-login-problem/#Item_8 was incorrect. The problem occurs on both IE and Firefox and oddly seems to be "cleared" by logging in successfully using a different username. I'm wondering if it has something to do with people not logging out of the application and cookies not expiring correctly.
Unlike the first report of the problem, the 2nd attempt also fails, as does the 3rd, 4th, etc. Similar to the first report though, the URL after the failure shows: people.php?PageAction=SignOutNow...
For what its worth, we figured out the problem. I'm posting it here in case any one else runs into a similar problem. Basically, this is a problem that occurs because IIS is NOT case sensitive. The primary link to the vanilla installation was something like mywebsite.com/Vanilla whereas it was configured in vanilla as mywebsite.com/vanilla. So there was a disparity between the URL and the cookies and the cookies couldn't do their job.