Advanced search  

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

Pages: [1]   Go Down

Author Topic: Upgrade results in fatal error  (Read 5303 times)

0 Members and 1 Guest are viewing this topic.

Veronica210

  • Coppermine newbie
  • Offline Offline
  • Posts: 15
Upgrade results in fatal error
« on: August 31, 2007, 06:16:00 am »

This has not been a good day. First I was hacked, then after finding the hacked code and removing it I actually had my Coppermine running perfectly again.

Then I made a stupid mistake of replacing the repaired files with cleans one I had in a backup drive on my folder...no idea what happened but it killed Coppermine. So I decided to upgrade. I followed the instructions for 1.4x to 1.412 keeping my albums, keeping anycontent.php and keeping my config.inc.php files.

The Update gave two errors:
Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /var/www/vhosts/mysite.com/httpdocs/photos/update.php on line 47

Warning: mysql_free_result(): supplied argument is not a valid MySQL result resource in /var/www/vhosts/mysite.com/httpdocs/photos/update.php on line 50

any help would be greatly appreciated...what a day it's been
:(


Navigating to index.php gives this error
While executing query "SELECT * FROM cpg132_config" on 0
mySQL error: Table 'mytable.cpg132_config' doesn't exist

(mytable has been replaced to protect my database name)

note: cpg132 was my existing database on the cpg149 tables appear as well when i checked my control panel (Plesk) after the update.
« Last Edit: August 31, 2007, 08:01:35 pm by Nibbler »
Logged

Veronica210

  • Coppermine newbie
  • Offline Offline
  • Posts: 15
Re: Upgrade results in fatal error
« Reply #1 on: August 31, 2007, 06:22:24 am »

if this helps, these are tables i now have after the update:
cpg132_banned
cpg132_bridge
cpg132_dict
cpg132_ecards
cpg132_exif
cpg132_favpics
cpg132_filetypes cpg132_hit_stats cpg132_plugins cpg132_sessions cpg132_temp_data cpg132_vote_stats cpg149_albums cpg149_banned cpg149_bridge cpg149_categories cpg149_comments
cpg149_config
cpg149_dict
cpg149_ecards cpg149_exif cpg149_favpics cpg149_filetypes cpg149_hit_stats cpg149_pictures cpg149_plugins cpg149_sessions cpg149_temp_data cpg149_usergroups cpg149_users cpg149_vote_stats cpg149_votes
Logged

Veronica210

  • Coppermine newbie
  • Offline Offline
  • Posts: 15
Re: Upgrade results in fatal error
« Reply #2 on: August 31, 2007, 06:28:22 am »

sorry for the 3rd post, no edit? i'm exhausted and can't think straight
my upgrade was from 1.49....not 1.32....yet these are tables showing in Plesk....
the config for 1.32, as per the fatal error message, is not there.
Logged

Nibbler

  • Guest
Re: Upgrade results in fatal error
« Reply #3 on: August 31, 2007, 04:19:58 pm »

MAke sure the info in include/config.inc.php points to the tables with your data.
Logged

Veronica210

  • Coppermine newbie
  • Offline Offline
  • Posts: 15
Re: Upgrade results in fatal error
« Reply #4 on: August 31, 2007, 07:43:42 pm »

ok that was it.

You have no idea how helpful that was!
thank you so much.
:)
p.s. is it normal to still have 1.3 tables (as posted above) along with the 1.4.9s?

the next step for me is to understand how my coppermine was hacked (wordpress was hacked at the same time but none of my other cms applications for example phpbb and pixelpost were not affected).

again
THANK YOU SIR!!!!!!!!!!!
Logged

Nibbler

  • Guest
Re: Upgrade results in fatal error
« Reply #5 on: August 31, 2007, 08:01:08 pm »

No. All table prefixes should be the same. You can backup and remove any duplicate tables.
Logged
Pages: [1]   Go Up
 

Page created in 0.044 seconds with 19 queries.