http://drupal.org/node/14563#comment-110435
Major bug in this thing...
The session managaer cant handle FireFox...
Its ok in Internet Explorer, but not in FireFox.
You need to log in on forums and on drupal seperately with FireFox...
And you CANNOT log off the forums within drupal using FireFox, only way is to delete the appripriate cookies, but this is not very comfortable.
I cant quite understand these linse:
RewriteCond %{QUERY_STRING} ^sid=(.*)$
RewriteRule ^login.php(.*)$ ../drupal/user/login?destination=phpBB2 [L]
In .htacess in forum folder.
If there is no sid, then you can actualy avoid drupal login, and log in to the phpBB, without logging in to drupal. So now if u want out of the forums, u have to log in to drupal and log out again. Quite confusing.
Im dont know much about cookies, so could someone suggest something about this ? Please.
Comments
Comment #1
arkepp commentedThis really doesn't make a whole lot of sense to me right now, but I will have another look at it tomorrow and appreciate that you suggest a fix.
I've made a number of changes that will be comitted to CVS at the same time.
Comment #2
arkepp commentedA bunch of stuff has been comitted to CVS, but none of it affects sessions-handling as far as I can remember or see from the diffs.
I havent been able to replicate anything like the situation you describe. I run Linux and use Firefox almost exclusively, I only have someone test with Internet Explorer at the last minute. Perhaps there is an issue with the naming of the cookies, capitalization or dashes or something similar.
My installations of phpBB tended to append a SID to the URL before logging someone in. I am a bit reluctant to change this right now, because I know the current setup works on my installations and I won't get a chance to test the change for another two weeks. Drupal 4.7 is something I currently only run on test-installations.
So did removing the SID-clause actually solve any problems for you? If it did and someone else running 4.7 can vouch for this, I'd be happy to remove the clause and move the statement to the end.
Comment #3
icenogle commentedI can confirm there is a problem here. I've been waiting for it to show up, here, to make sure it wasn't something unique to my setup.
I think it may have to do with intermixing IE and Firefox usage. When I'm experiencing the problem, I can't log on with Firefox. It doesn't produce any error message -- It simply returns me to the log in form, over and over. I know there is a problem with the cache being turned on and Drupal getting confused about log on status, and I have caching turned off, as a result, and I have flushed the cache. So this isn't that problem.
This problem likely shows up more for those of us who spend lots of time making sure different browsers work and different user configurations work (e.g. taxonomy access). So we do lots of logging on and off.
Comment #4
icenogle commentedSorry, I just noticed which project this bug is logged against. I'm not using phpBB, but I do experience session control problems when intermixing IE and Firefox, so it may be likely the problem is not in the phpBB module, but in the core instead.
Comment #5
jase951 commentedHave you tried to empty the sessions table?
I sometimes get errors about sessions when I log in - though I still get logged in. I empty the sessions folder for both phpBB and drupal and after a while seems theres no problem.
Comment #6
smilodon commentedI can 100% say, that to emty session table has no effect.
Emtying chache will aslo not help. It's not in core, its because the two browsers handle the cookies differently.
Here is the thing
You log in with IE, two cookies are created
If i do the same with firefox, then three cookies are created:
The BOLD cookies are for the phpBB dorums, i named them BBSESSID.
As you can see the bolded crypted password is different (false) in the firefox raw cookie file.
But the IE creats the it right, and it is usable.
If u now go on forums with firefox, then it creates a GUEST session for you... it is the italic cookie.
Comment #7
arkepp commentedI have assigned this to Drupal since it, based on your comment, has nothing to do with my module.
I find it highly unlikely that this is a bug in the code, since the forums would be flooded if everyone was experiencing this, and have therefore changed it to a support request and changed to priority to normal. I guessed 4.6.6, since 4.7 was not out at the time.
I hope this is okay, best of luck.
Comment #8
smilodon commentedI belwave it is earlyer version. 4.6.3
Im moving to drupal 4.7, but this will take a lot of time... testing all the modules and transfering data from one to another. Then creating new theme, language files etc..
Comment #9
magico commented@smilodon: anything new? If not, can we close this?
Comment #10
magico commentedI don't have any problem with 4.6.10
Comment #11
(not verified) commented