Updating to 1.3.3, - what about bridging to phpBB and the private albums Updating to 1.3.3, - what about bridging to phpBB and the private albums
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Updating to 1.3.3, - what about bridging to phpBB and the private albums

Started by Neologist, May 08, 2005, 01:32:04 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Neologist

Hello,

I've installed Coppermine 1.2.1 on my site, running as a bridged version with phpBB 2.0.15.
Now I want to update the gallery to 1.3.3, but I did not figure out a way to keep the bridging and the private albums as they are.
Is there a way to do so?

Links to my site:
Main Site with phpBB: http://www.abimanie.de
Gallery: http://photos.abimanie.de
They both got the same database.

Joachim Müller

  • backup your current bridge file
  • do the upgrade as suggested in the docs (this means: overwrite the old bridge file and init.inc.php with new versions as well)
  • re-apply the bridging steps (take a look at you old bridge file if you don't remember what values you need to enter, that's why you're suppossed to keep the old bridge file) by modifying the new phpbb bridge and init.inc.php
You won't lose any privacy information (as it is stored in the database, not the files).

Joachim

Neologist

Ok, everything went fine ... nearly everything.
Now I have just a little bug left. With some kind of mod I created a link in phpbb beneath the avatar for direct access to the private albums of the user. Just take a look at this: http://abimanie.de/viewtopic.php?t=566&postdays=0&postorder=asc&start=585. The link "Photogalerie" will work with all users exept of myself ("David").
Can somebody tell me, whats the failure here? Instead of index.php?cat=10001 he calls index.php?cat=2. That does not make any sense to me.
I think that there's somethig wrong in the database ... but where?  ;)