[Solved]: From 4.16 to 4.17 - Getting sql at top of page [Solved]: From 4.16 to 4.17 - Getting sql at top of page
 

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]

Main Menu

[Solved]: From 4.16 to 4.17 - Getting sql at top of page

Started by cryptq1, April 12, 2008, 02:19:44 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

cryptq1

Hi

I've followed all the steps for upgrading from 1.4.16 to 1.4.17.  I have run into one problem that is being caused by the /bridge/coppermine.inc.php file.

The following appears at the top of every page in my gallery:

Quote= $i_group_name) { cpg_db_query("UPDATE {$CONFIG['TABLE_USERGROUPS']} SET group_name = '" . addslashes($i_group_name) . "' WHERE group_id = '$i_group_id' LIMIT 1"); } } // fix admin grp if (!$this->use_post_based_groups) cpg_db_query("UPDATE {$CONFIG['TABLE_USERGROUPS']} SET has_admin_access = '1' WHERE group_id = '1' LIMIT 1"); } } // and go ! $cpg_udb = new coppermine_udb; ?>

I've managed to get rid of it by commenting out the following lines in coppermine.inc.php, around line 423:

foreach($udb_groups as $i_group_id => $i_group_name) {
    if ($cpg_groups[$i_group_id] != $i_group_name) {
    cpg_db_query("UPDATE {$CONFIG['TABLE_USERGROUPS']} SET group_name = '" . addslashes($i_group_name) . "' WHERE group_id = '$i_group_id' LIMIT 1");
    }
    }


The gallery seems to work fine without this, but I'm not at all sure what this will break in future. Btw, the gallery is running as a stand-alone although I previously had Mehdi's joomla bridge installed.

Any assistance will be appreciated.

Joachim Müller

If code shines through the pages, one of your files is corrupted. Re-download the package and perform an upgrade once more.

cryptq1

Hi

Ok, did that, took a while as I have a few changes that I have to make to many files, eg additional custom fields. However the same problem still exists. I suppose that I could have made exactly the same mistake twice, although I would regard it as unlikely as I use file comparison software.

Anyway if the coppermine.inc.php file is only used for bridging I'm not going to get excited by this. If you could see any potential problems, except bridging, that I'm unaware off please post them here else I'm going to regard this as a non-issue and resolved.

Regards
Etienne

cryptq1

Maybe I should mention that the gallery functions 100% from what I can see, it displays as expected, uploads, deletes, comments, voting, editing 1 or multiple files all functioning.

cryptq1

Right, I've no idea how all this fits into each other but 4.18 has solved this problem. :)