Problem with upgrade from 1.2.1 to 1.3.2 Problem with upgrade from 1.2.1 to 1.3.2
 

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

Problem with upgrade from 1.2.1 to 1.3.2

Started by blfarris, January 03, 2005, 02:36:35 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

blfarris

I was changing hosting providers and decided to upgrade Coppermine at the same time. 

The steps I followed were:

1. Upload 1.3.2 files to new host
2. Create new database and user for same
3. Run install.php
4. Delete the db that it created.
5. Upload the old db (V 1.2.1)
6. Run update.php (completed with no errors)
7. When I continue on to index.php I get: "Fatal error : There was an error while processing a database query"
8. Search forums and find note to change debug_mode in cgp11d_config to "1"
9. Open PHPMyAdmin and change debug_mode to 1
10. When I hit index.php I get the same error "Fatal error : There was an error while processing a database query"
In fact I get that error when I hit any page in the cpg directory (i.e. versioncheck.php or phpinfo.php)

Any thoughts?

Brad

Tranz

Did you edit the /include/config.inc.php file to match your new hosts' db settings?

blfarris

Because I did a "virgin install" of 1.3.2 on the new server the config.inc.php file has all the info appropriate for the current server.

Before I uploaded the old db, I was able to load index.php, it's only after dropping that table, then uploading the old file and running update that I started having the propblem.

But just in case, I just looked at it and it is indeed the updated info.

But now you have me thinking...

One of the fields in that file is $CONFIG['TABLE_PREFIX'] =                'cpg132_';

When I browse the db, I have some with cpg11d_ for a prefix (including config) and others with cpg132_.  I assumed that the cpg132_ were added during the update process, but should the update process change this setting too?

>> Ok, I tried changing that to cpg11d_ and it still had the same error message...

Brad

Joachim Müller

the steps you did (decribed in your first post) are not the steps recommended in the docs. Moving servers and updating at the same time is not a good idea imo, you should make this a 2-step process instead. Since you should have the backup files from your old host, I suggest you start over on your new server.
Recommended steps:
1) Upload all files from your old server to the new one
2) Restore the database dump from the old server to your new one (using phpMyAdmin)
3) Edit include/config.inc.php to refelct the different database settings
4) browse your coppermine page on the new server
5) log in as admin
6) go to config, change "target for ecards" settings to reflect your new url (if it changed)
7) Test drive your cpg1.2.x install on your new server (make sure everything works as expected)
8) Download the cpg1.3.2 package, unzip it and browse the docs folder, read the update instructions and do as suggested there

Joachim