News:

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

It work fine Usergroups, usernames and I guess also all right-settings (I have checked only two, but I am sure that all other will also work).

I only have some problems with the collation / character encoding but I guess this is a problem from the database collation (UTF8 works fine for the gallery phrases, Western-ISO 8859-1 works fine for the usernames with german characters).

I want to learn what I made wrong I don't understand your link. This is just for information that the bridge works fine because I found nothing about vB 4.0 in the forum (and vB3 is only named in the Bridge Manager).I can't post a link because my installation is only a non-public testversion (licence agreements of vB: use only 1 installation with public access).

I wrote the note for collation incompatiblity because it happened to my test. But I' am sure that this is a problem of my installation and not a problem of the bridge

I have had problems with the cookie salt in a older version after an update.vBulletin changed the value of the cookie_salt from the licence number to a random number which comes with the download.The value is written in the file /includes/function.php of vB

I have also vbulletin 4.0.1 installed and after this I can not connect anymore to the coppermine gallery.After typing the link to the gallery I see login and when I click this I come to the starting page of my forum.

make a test account with no further rights. The support don't need a admin account!Only a standard user... So that Joachim can see what happens with the cookies.And after Joachim tested this, you can delete this user.

@JoachimAs I wrote you in the thread, I have no public version, only a testversion. I ask for a hint to find the problem, I don't asked for a solution

And my first post was only posted to let you know that vB 4.0 will work fine with the bridge, I don't asked for support.

At vB devs:Your proposed fix is to populate a third-party file (coppermine's include/config.inc.php, seen from your perspective, is a third party file) with a variable from your app? And that is supposed to be a true, genuine fix?I'm not a vBulletin expert, but as far as I can see you store your settings inside the $config array, which is available for processing for third party apps (that's what the coppermine bridge for vbulletin does): we use PHP's require_once command to include vB's file includes/config.php. The corresponding code in bridge/vbulletin30.inc.php is $this->boardurl = $BRIDGE['full_forum_url']; require_once($BRIDGE['relative_path_to_config_file'] . 'includes/config.php');$this->use_post_based_groups = $BRIDGE['use_post_based_groups'];This is meant to give us access to all of your settings inside the $config-array, as we later use// Running on vBulletin 3.5.x$this->db = array('name' => $config['Database']['dbname'],'host' => $config['MasterServer']['servername'] ? $config['MasterServer']['servername'] : 'localhost','user' => $config['MasterServer']['username'],'password' => $config['MasterServer']['password'],'prefix' => $config['Database']['tableprefix'] );Due to vB not being FOSS I don't have a copy of vB to test this, so I can't tell for sure. But judging from the fact that manually populating $config['Misc']['cookieprefix'] = 'bb_'; in a coppermine file fixes the issue for the posters here means that the scope of that variable is wrong in your application or that it get's populated at a later stage. The expected reply from vB staff would have been "we don't support third-party applications like Coppermine", which is at least what we tell users who ask questions about vBulleting on our forum. Blaming Coppermine to be at fault sounds lame to me though: upgrading your app broke the bridge, and it turns out that it happens because of something the vB devs changed in vBulletin (changing the cookie prefix from "bb" to "bb_").We (the Coppermine developers) are not fond of a proposed "fix" that requires editing a coppermine component that is not related at all. If you must edit a coppermine file, edit bridge/vbulletin30.inc.php and add your proposed change there. Even better would be not to require end user to edit that file at all by modifying coppermine's bridge file with a little if/then toggle:

if (vB-Version >= 4) { $config['Misc']['cookieprefix'] = 'bb_';}would do the trick - we just need to figure out where the version number of vB is kept (in which variable or constant that is available for the third-party page). So my question at the vB devs is: is there a varibale that we could use, or do you have another proposal.

Joachim Müller (aka GauGau)- Coppermine project manager -

I have moved your thread to the testing/bugs board, although this is not a genuine coppermine "bug".