Redundant database tables after upgrade Redundant database tables after upgrade
 

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

Redundant database tables after upgrade

Started by Bill Roberts, February 28, 2009, 02:47:10 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Bill Roberts

I just upgraded to 1.4.20 and it works!

Now I have what appears to be a duplicate set of tables in the database, one prefixed cpg14x and one prefixed cpg132.

Are they redundant and can I safely drop the cpg132 tables?

Nibbler

That means you didn't upgrade correctly. Check include/config.inc.php and see what prefix Coppermine is actually using.

Bill Roberts

// MySQL TABLE NAMES PREFIX
$CONFIG['TABLE_PREFIX'] =                'cpg132_';

Can I edit the file to correct it?

Or is it more complicated?

Nibbler

Don't change the file. That means you can drop the cpg14x tables. Check them first though to make sure they don't have anything you want.