Fatal Error after 1.4.3 Upgrade. Fatal Error after 1.4.3 Upgrade.
 

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

Fatal Error after 1.4.3 Upgrade.

Started by Cyberpawz, February 21, 2006, 06:12:55 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Cyberpawz

I am getting a Fatal Error, I have followed the directions... I am upgrading from 1.3.5 to 1.4.3, and as of now nothing works, thankfully this is a backup but still...I am not happy, I can't upgrade at all... I can't side grade, and as far as I can tell I can't do squat... I need help and I'm getting lost in the process...

This is what I am reading...

http://www.cyberpawz.com/Coppermine2/docs/index.htm#13

And this is what I get as results...

http://www.cyberpawz.com/Coppermine2/

Something isn't right in Denmark, and it's not me. On that note, whenever I do the update.php it seems for some reason the updates aren't taking, but all folders and subfolders, and files have the CHMOD of 777

http://www.cyberpawz.com/Coppermine2/versioncheck.php

Oh, and this is what my database looks like now...thankfully it hasn't messed up the old server at all... and I do have backups thankfully even if it did.

(https://coppermine-gallery.com/forum/proxy.php?request=http%3A%2F%2Fwww.cyberpawz.com%2Fimages%2FPicture1.jpg&hash=e763c96f0e296a2193f95384dcb52f7757c04676)

kegobeer

1.  You uploaded all of the 1.4.3 files to your site?
2.  You ran the upgrade.php script?
3.  You are using the default theme, and not a custom theme?
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

Nibbler

Run a query to switch on debug mode.

UPDATE cpg11d_config SET `value` = '1' WHERE `name` = 'debug_mode' LIMIT 1

Cyberpawz

#3
Quote from: kegobeer on February 21, 2006, 06:40:45 AM
1.  You uploaded all of the 1.4.3 files to your site?
2.  You ran the upgrade.php script?
3.  You are using the default theme, and not a custom theme?

Yes to all three.

Quote from: Nibbler on February 21, 2006, 12:39:09 PM
Run a query to switch on debug mode.

UPDATE cpg11d_config SET `value` = '1' WHERE `name` = 'debug_mode' LIMIT 1

Still a Fatal Error.

Nibbler

Open include/functions.inc.php, find


        if (!$CONFIG['debug_mode']) {
            cpg_die(CRITICAL_ERROR, $lang_errors['database_query'], __FILE__, __LINE__);
        } else {


change to


        if ($CONFIG['debug_mode'] === '0') {
            cpg_die(CRITICAL_ERROR, $lang_errors['database_query'], __FILE__, __LINE__);
        } else {

Cyberpawz

#5
Quote from: Nibbler on February 21, 2006, 03:07:04 PM
Open include/functions.inc.php, find


        if (!$CONFIG['debug_mode']) {
            cpg_die(CRITICAL_ERROR, $lang_errors['database_query'], __FILE__, __LINE__);
        } else {


change to


        if ($CONFIG['debug_mode'] === '0') {
            cpg_die(CRITICAL_ERROR, $lang_errors['database_query'], __FILE__, __LINE__);
        } else {




Parse error: parse error, unexpected T_STRING in /Volumes/Server/htdocs/Coppermine2/include/functions.inc.php on line 240

Which is the code you told to me paste in...

or specifically

          cpg_die(CRITICAL_ERROR, $lang_errors['database_query'], __FILE__, __LINE__);

Shouldn't it be...


    if (!$CONFIG['debug_mode'] === '0') {
            cpg_die(CRITICAL_ERROR, $lang_errors['database_query'], __FILE__, __LINE__);
        } else {


Instead of


    if ($CONFIG['debug_mode'] === '0') {
            cpg_die(CRITICAL_ERROR, $lang_errors['database_query'], __FILE__, __LINE__);
        } else {

Nibbler

There is nothing wrong with the code I posted.

Cyberpawz

Ok, this is a little odd... my original database looks like it got afflicted with a 1.4.3 bug by accident... as well as some of the PHP coding as well...

http://www.cyberpawz.com/coppermine/index.php

Is there any reason why this is happening? Also how do I fix this without destroying it... I can't afford to have this be ruined on me, this is live data, and I have too many people relying on me to keep this up and running right now to take it down.

Cyberpawz

Quote from: Nibbler on February 21, 2006, 03:34:03 PM
There is nothing wrong with the code I posted.

That's fine, but why isn't my coppermine site working now? Or correctly?

Something has to be wrong somewhere.

Tranz

It looks like you included the gallery code an additonal time. Redownload a fresh copy from our site and upload the unmodified files.

Tranz

Make sure you're not using a wysiwyg editor that messes with code. Use wordpad and save as text-only.

Cyberpawz

Quote from: TranzNDance on February 21, 2006, 04:39:00 PM
It looks like you included the gallery code an additonal time. Redownload a fresh copy from our site and upload the unmodified files.

http://www.cyberpawz.com/Coppermine3/

Just did, same issue.

Cyberpawz

Quote from: TranzNDance on February 21, 2006, 04:40:11 PM
Make sure you're not using a wysiwyg editor that messes with code. Use wordpad and save as text-only.

I'm using BBEdit 8, as far as I know I've never had any problems with the program....

Tranz

According to the source code, it's v. 1.3.5. Make sure your ftp app overwrites existing files and that you're uploading php files in ascii not binary.

Cyberpawz

Quote from: TranzNDance on February 21, 2006, 05:00:17 PM
According to the source code, it's v. 1.3.5. Make sure your ftp app overwrites existing files and that you're uploading php files in ascii not binary.

I got it working, for some reason the 1.4.3 I downloaded before was corrupted... it's working fine under www.cyberpawz.com/Coppermine/