bridge: joomla 1.5.6 and coppermine 1.4.19

[katim110]

Hi all,

I tried... I really tried but this time I need your help.
I have Joomla 1.5.6 and the latest Coppermine 1.4.19 with the bridge component installed. I think I did everything in the FAQ page,  but when i come to this (see the screenshot) i dont know what I have to fill in
please help
Thanks for your help.

http://img246.imageshack.us/img246/7168/74040526us2.jpg [Edit GauGau] Replaced hotlinked image with attachment [/Edit]

[Joachim Müller]

I think I did everything in the FAQ page

No, you have not done as suggested. From the sticky thread on this sub-board named "When requesting bridge support - mandatory!":

When requesting bridge support, please post a link to your site, a test user account, and what you have set in the bridge manager.
Make sure that the test user account doesn't have admin privileges. When posting parts of your bridge file, make sure to replace passwords with asterisks.

This is how your posting should look like (with actual URLs instead of the dummy URLs I posted as an example):

I have the following issue when trying to bridge coppermine and XXX:
[error message here]

Coppermine install: http://mysite.tld/my_coppermine_folder/
Forum install: http://mysite.tld/my_forum_folder/
Coppermine version: cpg1.4.2
Forum version: SuperDuper BBS app v0.8.15
Test user account: some_testuser_name / the_password_for_the_test_user_account

BridgeManager settings:
Forum URL:  http://mysite.tld/test/foo_bar
Relative path to your BBS's config file:  ../bla/
Use post-based groups?:  0
Cookie name/preifx (if applicable)

Do not reply to this thread with individual support requests or similar - this is an announcement thread! Start your own thread instead.

Joachim

From the corresponding section of the docs:

Bridging support

With the explanations given above you should be able to bridge your (BBS) application with Coppermine. However, if things don't work as expected, you're welcome to look for help using the coppermine support board. When asking for support, please keep in mind that the supporters will need some information to enable them to help you:

    * Search the board before posting - maybe somebody had similar issues to yours that have been solved already
    * Post on the board that deals with your version - bridging mechanisms have changed from version to version, that's why it's important to post on the board that actually corresponds to your coppermine version
    * Don't hijack threads - when looking for bridging support, start your own thread
    * Read the sticky threads before posting
    * Make sure you are using the latest versions of the bridging files, they are kept up to date between formal Coppermine releases. Download the relevant files from the SVN. Update udb_base.inc.php and the file that corresponds to the bridge you are using and upload them into your bridge directory, overwriting the old ones. Of course you should make sure to use the most recent stable coppermine release in the first place.
    * When requesting bridge support, please post a link to your site, a test user account, and what you have set in the bridge manager.
      Make sure that the test user account doesn't have admin privileges. When posting parts of your bridge file, make sure to replace passwords with asterisks.
       
      This is how your posting should look like (with actual URLs instead of the dummy URLs given here as an example):

I have the following issue when trying to bridge coppermine and XXX:
      [error message here]

      Coppermine install: http://mysite.tld/my_coppermine_folder/
      Forum install: http://mysite.tld/my_forum_folder/
      Coppermine version: cpg1.4.19
      Forum version: SuperDuper BBS app v0.8.15
      Test user account: some_testuser_name / the_password_for_the_test_user_account

      BridgeManager settings:
      Forum URL:  http://mysite.tld/test/foo_bar
      Relative path to your BBS's config file:  ../bla/
      Use post-based groups?:  0

I can't see that you did as requested there. Instead, you hotlinked a screenshot in a language that we're not familiar with. Not a bright idea.