Advanced search  

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]

Pages: [1]   Go Down

Author Topic: Redundant database tables after upgrade  (Read 5125 times)

0 Members and 1 Guest are viewing this topic.

Bill Roberts

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
Redundant database tables after upgrade
« on: February 28, 2009, 02:47:10 am »
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?
Logged

Nibbler

  • Guest
Re: Redundant database tables after upgrade
« Reply #1 on: February 28, 2009, 04:10:23 pm »
That means you didn't upgrade correctly. Check include/config.inc.php and see what prefix Coppermine is actually using.
Logged

Bill Roberts

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
Re: Redundant database tables after upgrade
« Reply #2 on: March 01, 2009, 08:35:55 am »
// MySQL TABLE NAMES PREFIX
$CONFIG['TABLE_PREFIX'] =                'cpg132_';

Can I edit the file to correct it?

Or is it more complicated?
Logged

Nibbler

  • Guest
Re: Redundant database tables after upgrade
« Reply #3 on: March 01, 2009, 05:20:46 pm »
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.
Logged

Bill Roberts

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
Re: Redundant database tables after upgrade
« Reply #4 on: March 01, 2009, 06:33:06 pm »
thanks
Logged
Pages: [1]   Go Up
« previous next »
 

Page created in 0.021 seconds with 19 queries.