Links in coppermine to profiles...bridged with invision board 2.0

[djsckizo]

I'm using Coppermine 1.3.2 and Invision Board 2.0, with the bridge for IB2 from the download area of sourceforge.net, and have noticed that the links to profiles go to the coppermine profiles instead of the invision board profiles. I'd rather have them go to the IB ones since they are completely filled out, and the forum is what I'm trying to focus on. Did I do something wrong, or are they supposed to point to the coppermine profiles?

[Joachim Müller]

link & test user account please.

Joachim

[Casper]

Have you tried using the bridge file supplied with coppermine.  This does use the bulletin board user profile.

[djsckizo]

link & test user account please.

Joachim

http://www.sidebreak.com/forum/
http://www.sidebreak.com/imagehost/

username: coppermine
pass: test

[Joachim Müller]

did you do what Casper suggested?

Joachim

[djsckizo]

no, actually i didn't. i had a problem with my browser and antivirus program hating each other and didn't get back until now. i'll try that now and let you know if it worked

[djsckizo]

ok. i tried that. when i did that, i get an error that (with the debug turned on) is looking for "password", but ib has it set as "legacy_password", not just "password".


edit: after reading more through the coppermine forums, I see that you guys won't be dealing with the bridges any more, but rather focusing on the coppermine software. I've asked on the Invisionize.com forum about this problem I'm running into. Thanks for trying to help though. Keep up the good work with the software.

[Nibbler]

The IPB 2 bridge is a user contribution, so we can only help you to a certain extent. It is normal behavior for the profile to go to coppermine's own profile, making it work differently would currently require you to change the links in coppermine's code.

[Joachim Müller]

after reading more through the coppermine forums, I see that you guys won't be dealing with the bridges any more, but rather focusing on the coppermine software.

How do you come to this conclusion? We still support bridging, we're even adding new features for the next version of coppermine. The only thing we do not support is the third party hack "coppermine goes invisionize", as it's not only a bridge file, but involves changes in the core code of coppermine, with changes that create problems that don't exist in the "regular" coppermine package. We consider the fact that coppermine can be easily bridged with a lot of apps one of the main features of coppermine, we even encourage people to write and publish even more bridge files for other apps, we just don't like third party hacks that modify the coppermine core code and then don't support those modifications, but send frustrated users to our page. It's only natural that they're upset if we tell them we can't help, as we don't know the modifications they applied. My vision would be that those third party apps that need to modify coppermine core code don't call themselves "bridge files" (which they are not), but ports that need to be supported by their creators, not by the team on this board.

Joachim