Advanced search  

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]

Pages: [1]   Go Down

Author Topic: No error, but it did not work ...  (Read 2885 times)

0 Members and 1 Guest are viewing this topic.

LokisFeuer

  • Coppermine newbie
  • Offline Offline
  • Posts: 2
No error, but it did not work ...
« on: February 27, 2008, 12:52:11 pm »

I have the following issue when trying to bridge coppermine 1.4.16 and vBulletin 3.6.8:

No error, it simple don't work.
If I activate the bridge I can't see anything, see more at the end of the post.

Coppermine install: http://astkm.de/galerie/
Bridging app install: http://astkm.de/iforum/
Coppermine version: cpg1.4.14
Bridging app version: vBulletin 3.6.8 Patch Level 2
Test user account: Test/ Test
BridgeManager settings:
Bridge app URL:  http://www.astkm.de/iforum
Relative path to your bridge app's config file:  ../iforum/
Use post-based groups?:  1


CPG runs some time without bridging very well!
Updated CPG to actual version (from 1.4.9) and it went well (stand alone).
Now, after upgrading the board from a free version to vB we want to use the advantage of the bridiging.
For that I simple used the bridge-assistant.

I make several tries but non was working. When I activate the bridge, I can't work in CPG.
I've to deactivate the bridge direct in the DB.

Thanks for help!

MfG
Logged

Nibbler

  • Guest
Re: No error, but it did not work ...
« Reply #1 on: February 27, 2008, 01:14:49 pm »

You have you forum's cookie path set to /iforum/ instead of / and you are not consistent with www.astkm.de vs astkm.de
Logged

LokisFeuer

  • Coppermine newbie
  • Offline Offline
  • Posts: 2
Re: No error, but it did not work ...
« Reply #2 on: February 27, 2008, 01:46:32 pm »

Many thanks, what a quick help!
I make some changes in the cookie-setting, but I didn't change that option.

MfG
Logged
Pages: [1]   Go Up
 

Page created in 0.016 seconds with 15 queries.