• Resolved ancarett

    (@ancarett)


    I’m well aware I was running a really out of date installation of WordPress! I was finally inspired to update it today after my host upgraded MySQL to 5.0.51 and caused all my posts to display in backwards chronological order. *headdesk*

    I backed up my database and install files to my hard drive, then installed all the new WordPress files to my site. When I tried to run the upgrade.php, I get one of two error messages.

    If I define my db host with the numeric address (as I had to with the old install) in my wp-config.php I get THIS error message:

    Fatal error: Cannot redeclare check_admin_referer() (previously declared in D:\hshome\jliedl\ancarett.com\wp-includes\pluggable.php:339) in D:\hshome\jliedl\ancarett.com\wp-admin\admin-functions.php on line 474
    WordPress database error Table ‘jliedl_wp.wp_usermeta’ doesn’t exist for query SELECT meta_key, meta_value FROM wp_usermeta WHERE user_id = ‘2’

    There’s also a pretty extensive error message that shows up at the bottom of my main page — https://ancarett.com

    On the other hand, if I use ‘localhost’ in the wp-config.php file, I get the WordPress “Error Establishing a Database Connection” message page at upgrade.php AND the main page of the site doesn’t work at all (bold ERROR Establishing Database Connection”).

    So, obviously, I’m sticking with the first version of wp-config.php in order to have something up on my front page.

    I figured out that I’m still not connecting properly to my database. My question now is what questions do I need to ask of my host or find in myphpAdmin information in order to fix this?

    Thanks if you can help! If it takes trashing my very old theme and importing the old data in some new way, I can handle that, too.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter ancarett

    (@ancarett)

    Okay, I see that I’m supposed to upgrade to 1.5 FIRST. I try that and then I get this error message once I uploaded THOSE files and hit upgrade.php:

    Fatal error: Call to undefined function add_filter() in D:\hshome\jliedl\ancarett.com\wp-includes\default-filters.php on line 8

    That shows up both on upgrade.php and my directory home page whether or not I have the numeric address of the database in my wp-config.php file or not. Drat!

    Im going to point something out in your first post that may help you with what you are doing.

    Take a look at this error:

    Fatal error: Cannot redeclare check_admin_referer() (previously declared in D:\hshome\jliedl\ancarett.com\wp-includes\pluggable.php:339) in D:\hshome\jliedl\ancarett.com\wp-admin\admin-functions.php on line 474

    Now, since you said you have the 2.3.3 files on your own computer, take a look at wp-admin/admin-functions.php —

    what do you see?

    You do not see 474 + lines and you do not see any mention of that function.

    If I open up an archived zip of WordPress 1.5.2 I can look inside wp-admin/admin-functions.php and see that it IS in that version.

    IN other words, you didnt successfully update/upgrade/overwrite the OLD files, when you initially “installed” (your term used above) them to your site.

    Consequently, you had 2 versions of files on the site.

    That wont work.

    Until you insure that you only have ONE version of WordPress files on your site, regardless of what version it ends up being, youre going to have trouble.

    Thread Starter ancarett

    (@ancarett)

    Thank you! You’re right — in all the frustration (I spent a few hours banging my head against the PHP version upgrade) I obviously bolluxed my file folder tracking. I wiped it all out, downloaded the upgrade version again and reinstalled cleanly. (1.5.2)

    I got to the upgrade page that seems to have correctly established a connection to the database. Yay! But the upgrade stalls — it loads only to ?step=1 and has been stuck at that for 15 minutes (the browser status bar for the page says that it’s done loading).

    Is this possibly due to folder permissions on wp-admin? I’m having difficulties in changing the permissions (can’t do it via FTP) on wp-admin folder and I suspect that is the problem.

    not really no — directories ought to be 755, which it sounds like they are since you can access the files within, and files ought to be 644.

    Thread Starter ancarett

    (@ancarett)

    Drat. I was hoping it would be something relatively straightforward like file permissions (though I long for the good old days when hosts had plain vanilla access for chmod). I’m stumped trying to figure out why the upgrade is freezing the way it is. Hmm.

    Thanks anyway! I’ll look around the support forums a few more times to try and figure out where I went wrong.

    Still, I might ditch the old stuff and start over. I’ve done that once before when I moved from MT to WordPress — I have the database backed up and if I really wanted any old post, I could get the information out of the files.

    yah I dunno.. I wish you the best of luck though, you have an amazingly upbeat personality for someone having difficulties on here — most ppl arent quite so good natured ??

    Thread Starter ancarett

    (@ancarett)

    Hey, it’s not like this is your job (or that of anyone here). It’s an install/upgrade that I borked! Anyone needs a talking-to, it’d be me.

    As for the attitude, I spent three years of my life as support for an online community’s site-building system so I know that the only result of getting all worked up is that my blood pressure goes up.

    And it’s only a blog. I’ve killed it once already (and have the 1100 post backed up my first database archive). Might be time to kill it again. I’m thinking of setting up a new blog on a new domain — running WordPress, of course!

    Thanks again for your help. I’ll keep poking at possible solutions for a few days, maybe do a roll-back to the original install if I can’t get past this and want to preserve the archives. I just need to figure out what’s stalling the upgrade process. . . .

    Thread Starter ancarett

    (@ancarett)

    Okay, I dug around for a while and even though the upgrade.php file seemed to stall, I was able to open one of the back-end pages. It showed WordPress 1.5.2 installed so I went to Options, updated the Permalinks structure and, woot!, we’re back in action!

    I’m still not sure what was the problem, but navigating straight to the dashboard was probably what saved me.

    I’ll upgrade from 1.5.2 to one of the 2.0 versions as soon as I’m brave enough to tackle that mess. (Re-reading the documentation and the forum to figure out if I can go straight to the latest or have to make another intermediate step in the upgrade process.)

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Upgrade Problem from 1.12 to 2.33 (Database)’ is closed to new replies.