I tried to upgrade to 3.01 too, and here is MY error msg.

Check if the file /home/*****/public_html/wordpress/wp-includes/post.php exists and is readable. There seems to be a problem with the file permissions, assuming that the file exists. If the file permissions look alright, also check the directory permissions of /home/*****/public_html/wordpress/wp-includes.

Maybe I should re-upload all of the “includes” folder as some users seem to be doing? Recently when I got version 3 running, i had troubles with FTPing “simplepie”…lots of troubles…and of course I had to configure the config.php file.

I did notice something in passing, during the latest botched install, the file permission numbers appeared to be different, beginning with a 6 rather than a 7? Can’t remember the exact number, 644 maybe, and normally we see 755.

Hum, post.php, okay, I’ll go and look for that one… Got it, it looks perfectly readable, at least in the downloaded folder. Will have to go back to the server I have it on, to see what it looks like in there.

It wasn’t even in the folder! So I uploaded post.php and tried again to login. Now I get this:

Fatal error: require() [function.require]: Failed opening required ‘/home/a1958187/public_html/wordpress/wp-includes/pluggable-deprecated.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/a1958187/public_html/wordpress/wp-settings.php on line 180

Okay, I see in Filezilla there are lots of 644 permissions. Shouldn’t they all be 755? I’m not very knowledgeable about this…

Files should have 644 permissions, but directories need 755 permissions.

Oh! Right…and that does seem to be in order… ??

Sooooo. What now…?

wp-settings.php cannot include the script /home/a1958187/public_html/wordpress/wp-includes/pluggable-deprecated.php, so if this file exists, the directory permissions of /home/a1958187/public_html/wordpress/wp-includes or the file permissions of /home/a1958187/public_html/wordpress/wp-includes/pluggable-deprecated.php aren’t right.

But if you checked the permissions and they look alright, check if pluggable-deprecated.php is corrupted.

There is a pluggable.php file, but I didn’t find ‘pluggable-deprecated’. And the pluggable.php is perfectly readable.

Seems I may have seen the ‘deprecated’ file on the other server I’m using (a bit of shared space), so ASAP I’ll run over and look there. Not entirely sure about the permissions over there, either…

Ooh! It’s there, sure enough! And it’s readable. “Deprecated pluggable functions from past WordPress versions. You shouldn’t use these functions and look for the alternatives instead. The functions will be removed in a later version…Deprecated functions come here to die…” etc.

Permissions at the shared subdomain space look OK too.

It won’t help you on your other server though, you also need it on the server where the include fails according to the error message you’ve posted.

Oh…so I do need it to be inside the “includes” folder, correct? Well, I’m sure it could just be transferred in. Hm, I wish I could read these errors the way you guys do…! ??

And I quote you from earlier: wp-settings.php cannot include the script /home/a1958187/public_html/wordpress/wp-includes/pluggable-deprecated.php.

Should I be looking for “wrong” code in the wp-settings.php file?

*blueamulet feels like a certified Tech Dummy, lol*

Most likely there isn’t any “wrong” code in wp-settings.php, unless you modified it, of course. ??

But more to the point, you have to make sure that ALL the files that WordPress needs are in place.

Uhmrhm…I’ve done so much installing and re-installing and overwriting and downgrading and upgrading and chasing files around…LOL! Maybe the best option would be to clear it off yet again (what’s this now, the 11th time? I’ve lost count…) and give it another go??

At least now I know how to hack CHMOD, so if need be, I can also do that…!