coppermine-gallery.com/forum

Support => cpg1.3.x Support => Older/other versions => cpg1.3 Installation & Setup => Topic started by: thomasiam on October 05, 2005, 07:08:20 AM

Title: update error. upgrade from 130 to 135
Post by: thomasiam on October 05, 2005, 07:08:20 AM
HELP!!!!!!

I have upgraded from 130 to 135 few days ago and getting an error when I run update.php

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/lavaclix/public_html/gallery/update.php on line 38

Warning: mysql_free_result(): supplied argument is not a valid MySQL result resource in /home/lavaclix/public_html/gallery/update.php on line 41


when i look at the data base not all the pre fix has changed to 135

can some one tell me what this means and how I can fix this issue?

thank you in advance.

Title: Re: update error. upgrade from 130 to 135
Post by: Joachim Müller on October 05, 2005, 07:09:48 AM
make sure you have uploaded all files from the cpg1.3.5 package as suggested in the upgrade docs, and that the files have not got corrupted during upload.
Title: Re: update error. upgrade from 130 to 135
Post by: thomasiam on October 05, 2005, 07:25:42 AM
Quote from: GauGau on October 05, 2005, 07:09:48 AM
make sure you have uploaded all files from the cpg1.3.5 package as suggested in the upgrade docs, and that the files have not got corrupted during upload.

I just tied again with a new donload and copied the new set to the server with same result. any suggestion?  thanks
Title: Re: update error. upgrade from 130 to 135
Post by: Joachim Müller on October 05, 2005, 07:28:06 AM
use versioncheck.php to check if you have actually uploaded all files.
Title: Re: update error. upgrade from 130 to 135
Post by: Tranz on October 05, 2005, 07:47:35 AM
The table prefix should not have changed when you did the update. Do you mean to say the prefixes are a mixture of 130 and 135? Did you use the install.php file by any chance?
Title: Re: update error. upgrade from 130 to 135
Post by: Nibbler on October 05, 2005, 10:53:26 AM
Ensure you didn't edit config.inc.php and fiddle with the table prefix specified in that file.