Problem after upgrade CPG 1.3.2 to 1.3.4 Problem after upgrade CPG 1.3.2 to 1.3.4
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

Problem after upgrade CPG 1.3.2 to 1.3.4

Started by whmeeske, September 01, 2005, 11:03:52 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

whmeeske

I upgraded my CPG from version 1.3.2 to 1.3.4. I followed the instructions mentioned in the documentation. I did run update.php to get my DB's updated.
After this it should work, but instead of that I got a fatal error message when I opened CPG.

I checked my DB's with phpmyadmin and there I found out that only a few tables were renamed from "cpg132_..." to "cpg134_...".
I have renamed all the other tables manually and after that it was OK.

Why has that gone wrong with running update.php?

Nibbler

The tablename prefix is not supposed to change with the update.

whmeeske


Nibbler

Please describe exactly the steps you took to carry out the update.

whmeeske

Quote from: Nibbler on September 02, 2005, 12:19:50 AM
Please describe exactly the steps you took to carry out the update.
First I made a backup of my database, include/config.inc.php file and my albums directoy.
Then I unpacked the archive and put it on my webserver. After that I restored the include/config.inc.php file and my albums directoy.
In the include/config.inc.php file I changed the value of $CONFIG['TABLE_PREFIX'] from 'cpg132_' in 'cpg134_'.
Then I did run update.php, it gave no errors.
But when I tried to open my CPG in my webbrowser I got a fatal error.

I checked my DB's with phpmyadmin and there I found out that only a few tables were renamed from "cpg132_..." to "cpg134_...".
I have renamed all the other tables manually and after that it was OK.

Is there anything in the above what I should not have done?

Nibbler

Quote from: whmeeske on September 02, 2005, 11:21:52 PM
In the include/config.inc.php file I changed the value of $CONFIG['TABLE_PREFIX'] from 'cpg132_' in 'cpg134_'.

Why did you do that? That is not required or correct.

whmeeske

Quote from: Nibbler on September 02, 2005, 11:30:13 PM
Quote from: whmeeske on September 02, 2005, 11:21:52 PM
In the include/config.inc.php file I changed the value of $CONFIG['TABLE_PREFIX'] from 'cpg132_' in 'cpg134_'.

Why did you do that? That is not required or correct.
The table-prefix must be cpg134 instead of cpg132 or not? How can that be achieved in another way?

Nibbler

The table prefix does not change, ever. It will always be the same as when you first installed coppermine, no matter what updates you do.

whmeeske

Quote from: Nibbler on September 02, 2005, 11:42:12 PM
The table prefix does not change, ever. It will always be the same as when you first installed coppermine, no matter what updates you do.
OK, but isn't it kind of strange that prefixes are not the same as the current installed version?
Anyway, thanks for your information! I'm learning almost every day when I'm working with CPG and this forum helps a lot  :)

Nibbler

You can use any prefix you like, some people just use gallery_ or cpg_. It's just a name. :)