upgrade issue 1.3.3 to latest stable / Fatal Error

[gateway]

After updating my files on the server and following the upgrade procedure in the documentation im having issues now..

in the upgrade script everything was ok except at the bottom it spit out this info

Code Select Expand

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /usr/www/virtual/aquamann/www.mysite.com/members/photos/update.php on line 47

Warning: mysql_free_result(): supplied argument is not a valid MySQL result resource in /usr/www/virtual/aquamann/www.mysite.com/members/photos/update.php on line 50

then when I try to view any pages I get Fatal Error: with out any error messages, I enabled debug mode
as well but nothing is being spit out

thoughts?

[Nibbler]

Make sure the file include/config.inc.php has valid mysql connection information.

[gateway]

yea everything seems ok in the config.. .. the debug out put is showing up now i didnt do a refresh but here is what index.php says

Code Select Expand

While executing query "SELECT extension, mime, content, player FROM cpg133_filetypes;" on 0

mySQL error: Unknown column 'player' in 'field list'

[Nibbler]

Make sure your db user has the ALTER privilege and run the update.php again.

[gateway]

db user is root. it has all privs.. ..

[gateway]

also would like to say we have 2 coppermines running on our dedicated server the first upgrade went flawless, but this one is giving me hell.. i think the first one was 1.3.2 if that matters, and the one giving me issues is 1.3.3 version .. root is used for our db accounts for the coppermines..

[gateway]

further investigation is showing that the player field didnt get updated in this version.. Im compairing both db versions of coppermine, ie one working and one thats not.. teh player field is done in my 1.3.3 to latest upgrade..

[Nibbler]

update.php should have added that field.

[gateway]

I agree. any ideas ?

could i run each sql command from sql/update.sql file manualy to see where it barfs?

[Joachim Müller]

yes, that's an option. Don't forget to modify the table prefixes (although you seem to be knowing what you do, so the warning may be not necessary).

[gateway]

ok addig in player table and its values seemed to of worked...

i have no idea why the update script bailed on that.. could this be a related issue to 1.3.3 update to latest.. cause my 1.3.2 went smoothly.

[Joachim Müller]

I don't think so.

BTW: you mentioned that your db user is root - you shouldn't do that. Root has way to many privileges. As the server appears to yours to administer, I suggest creating a user with "regular" privileges, without the omnipotent ones (like GRANT).