PDA

View Full Version : Serious Cookie Problems


Lars-Christian
12-30-2004, 12:22 PM
I am currently working on setting up a system for my website, where I use three different scripts - Mambo (CMS), vBulletin (forum, duuh) and Coppermine (Image Gallery).

I have managed with some various bridge files / scripts to get them all to share the same user account, but now I am experiencing some problems with cookies, making the main site inaccessible.

This is the error msg I get:

Redirection limit for this URL exceeded. Unable to load requested page. This may be caused by cookies that are blocked.

I am really taking a shot in the dark here, but it seems to me as if the different cookies set by the three different scripts are conflicting with eachother for some reason.

You can check it out at :

http://www.zeldauniverse.net/index.php (site)

http://www.zeldauniverse.net/forums (forums)

http://www.zeldauniverse.net/gallery (gallery)

Haven't started the visual integration yet. Anyways, the problem seems to appear from time to time when you're going back to the main site - Could it be that the cookie expires there, but they are still "logged in", through the forums, or something like that?

I would appreciate any help I can get.

zachogden
01-01-2005, 09:23 PM
Wrong forum?

sicarius
01-03-2005, 11:09 AM
Well, I am tempted to move it to the Perl/CGI forum.

However, cookies aren't CGI and they aren't necessarily done in Perl.

Could be javascript. Who knows. General is OK by me.

stuka
01-03-2005, 11:56 AM
/me notes that at least one of the URLs ends in .php, so I'd suspect it's PHP coded pages.

zachogden
01-03-2005, 05:23 PM
Lars, may I ask why you have cookies set on all 3 pages? This could be the answer, as you suspected. Try just having cookies on the main page.

Whiteknight
01-03-2005, 11:13 PM
first off, I love zelda. your sight is awesome. second, you should be able to condense things down to a single cookie with multiple data fields. try to keep things simple: have a single page that creates a cookie when you "sign in", and have a single page that deletes the cookie when you "sign out." you shouldnt mess with the cookie anywhere else, except to change values, if necessary.