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.)

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. . . .

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.

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.

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!

‘Cause MT wouldn’t install on my latest host (Windows machine and the admins didn’t want to add some of the needed Perl bits). I’d been thinking about it for a while, anyways. Very, very, very glad I changed. The backend of WP has ten times the functionality of MT!

Thank you for this tip. I’d just started having this problem two days ago, couldn’t figure out what was the matter and now it seems fixed!

Now to study how to upgrade my installation and apply some of the more sophisticated anti-spam options. . . .