Advice on Fatal error: message when upgrading Advice on Fatal error: message when upgrading
 

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

Advice on Fatal error: message when upgrading

Started by camden, January 25, 2006, 06:47:56 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

camden

Hi all,

Apologies if this has been discussed elsewhere; I couldn't find a solution that worked for me (despite a number of people appearing to have similar/ related problems).

When upgrading from 1.3.5 to 1.4.3 the upgrade appeared to go smoothly (following the instructions) but I would get the dreaded 'Fatal error:' message with an empty page - no other info was on the screen.  I eventually remembered to turn the debug option on directly on the config table in the database, and the error - I'm afraid I cannot remember the exact words but it was a db permission problem - made me think of checking my mysql user permissions.  Sure enough, my user did not have 'alter' privileges.

The upgrade script actually gives a clue (if I'd read it properly).  On running it the first time it claimed that many of it's DB actions had been 'already done'.  Of course they weren't.  I guess the error handling in that script doesn't know about permissions errors (I'm not a php programmer so cannot check, unfortunately).

Providing that privilege - and if you don't have it you may need 'create' as well - solved my problem.  Run the upgrade script again, and voila - it all works!

Hope that helps someone out there.

Cheers,

Camden

Joachim Müller

you're right, this is a known issue: when running the update, the script runs the queries against the database, but doesn't check if they have been succesfully been applied. Alas it's a bit tricky to do that, and it would complicate the whole process of upgrading. I'm considering an extra function integrated into update.php (as well as the installer) that does some advanced checking of the database permissions for cpg1.5.x, so I'm moving this thread from the support section to the approved feature requests section, so this issue doesn't get overlooked. Thanks for bringing this up.

Joachim