Upgraded to IPB 2.2.1, Now Can't Login to Gallery Upgraded to IPB 2.2.1, Now Can't Login to Gallery
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Upgraded to IPB 2.2.1, Now Can't Login to Gallery

Started by St. Anger, December 25, 2006, 06:09:28 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

St. Anger

The integration between CPG and my IPB 2.1.7 forum was working fine. I upgraded to IPB 2.2 and it was still working fine, but then I upgraded to IPB 2.2.1 and now when I try to login to my gallery it redirects me to my forum's login page--but I'm already logged in there. I've tried clearing my cookies, but that didn't help. I've also tried rerunning the bridge, but that didn't work either. Can anyone please help me figure out hwo to fix it? I would appreciate it greatly.

Coppermine install: http://www.metcoverart.com/gallery
Forum install: http://www.metcoverart.com/forum
Coppermine version: CPG 1.4.2
Forum version: IPB 2.2.1
Test user account on forum: test/test

BridgeManager settings:
Forum URL:  http://www.metcoverart.com/forum
Relative path to your BBS's config file: ../forum/
Use post-based groups?:  1
Cookie name/prefix for forum: mcaforum_
IPB Cookie path: /
Cookie name/prefix for gallery: gallery
CPG Cookie path: /

Note: when viewing the forum, you can quickly get to the gallery by clicking on the Artwork Gallery link at the top left of any forum page, and there's a link back to the forum in the gallery too for easy access.

Thank you for any help, it would be very much appreciated.

St. Anger

I am going to upgrade to the latest version of CPG and try rebridging.

St. Anger

I've upgraded to CPG 1.4.10, but I still have the same problem as before... :(

Nibbler

IPB bridge is a user contribution that lacks support for a configurable cookie prefix. You will need to set the cookie prefix of your forum to blank in order to get around this.

St. Anger


mimins

Hello,

I have the same problem.

St. Anger, could you tell us what did you do exactly to solve this problem please ?

Thank you very much


Joachim Müller

The answer is already in Nibbler's posting:
Quote from: Nibbler on December 31, 2006, 12:47:47 AM
You will need to set the cookie prefix of your forum to blank in order to get around this.

If this doesn't solve your issue, start a thread of your own (doing as suggested in the sticky thread on this board). Locking.