3.01 Update – Failed and stuck! PLEASE Fix your upgrade!

Blackagave, you are a genius. I too have been struggling with 3.0 and 3.0.1 – but only on one installation of the 18 I work on. I’ve been putting off dealing with the manual install – dumb I know – but this trck worked like a charm.

Thanks for the tip.

I’ve been having the same upgrade issue with one of my clients and ended up having to add this to the .htaccess file so that the server software would pay attention to the settings in the custom php.ini file:

suPHP_ConfigPath /home/your_account

where “your_account” is your directory on your server.

sacredpath, that is really interesting and seems to agree with malaubli’s reinstall. What’s special about your custom php.ini I wonder?

Okay, we have a few POSSIBLE fixes:

1. Disable all Plugins and try again (from blackagave)
2. Recompile PHP (suPHP 5.3.3 from malaubli)
3. Force the server to point to YOUR php.ini by putting this in the .htaccess: suPHP_ConfigPath /home/your_account (from sacredpath)
4. Use the Memory Bump Plugin (someone over Twitter who’s name I just forgot…)

Also, we know that so far, a manual upgrade does NOT have any issues with people having the ‘cannot copy’ issue. Which, yeah, makes sense ??

And as freelancemom pointed out, IF it fails, you can ‘back out’ the upgrade by deleting the .maintenance file (found in the same folder as your wp-config.php file) and the upgrade folder (which is in the wp-content folder). Don’t worry about deleting those.

Can someone try this: Delete the upgrade folder and then try the automated upgrade again?

Forgot to mention above… once you delete the /upgrade folder you want to recreate it and set the chmod to 777.

ipesentu – I’ve deleted and retried multiple times without success.

Trying the .htaccess trick now ??

freelancemom – Thanks. Sometimes I’ve see the problem being the upgrade folder itself — basically it doesn’t have the right PHP permissions to do what it needs to do. That struck me a couple times in 2.x land, but was always fixed by a whack and reset.

I decided to give up and manually upgrade *all* my clients who are having this *same* issue. That way at least they’ll be able to use the wp admin to change themes and add plugins.

Hopefully the next release will address the issue — I’ve already spent an entire day on it.

ipsentu — the .htaccess line didn’t work for me. Good luck everyone!

freelancemom – Can you give us any specs on their servers? What version of PHP are they running, what version of Apache (or IIS) etc? Are they all using the same plugins etc?

It’s really hard to help debug when all you get is ‘it doesn’t work’ so anything you can provide may help the devs recreate the problem (some of us are nerdy enough to go an BUILD as matching a box as we can just to test this stuff… and to learn about how it all works)

Based on a user suggestion here, I had my hosting company install suphp and that solved the problem! Now all my upgrades and updates go through fine whereas before I was pulling my hair out trying to figure out the problem.

Wow, I had this problem earlier today, several times (“Unable to locate WordPress Root directory.”, 3.0.1, Swedish translation).

But upgrading the Contact Form 7 plugin first might have done the trick. Can’t think of anything else I did.

I manually upgraded and after uploading wp-admin and wp-includes as per instructions all I get is:
Fatal error: Cannot redeclare class WP_Http in /…/wp-includes/class-http.php on line 39

Then tied uploadoing a copy from my computer of the server files done three or four montss ago and I still get same fatal error.

Any suggestion about how to or what to look for to try recovering my pages.

Thanks

Any suggestion about how to

tarambana, that’s a different error. And you have your own post here: https://www.ads-software.com/support/topic/upgrade-gone-bad-help?replies=1

Bogarting someone else’s topic is bad form ??

Hi ipstenu,
err.. do you mean is nothing to do with trying to upgrade.
I don’t really know where to start an all I can get from my former websiate are fatal error notices!
Thanks nevertheless

Ah, and I didn’t mean to piggyback anyone’s topics! My apologies.

I was installing the update. Now, my blog is down, and I’m shut out:

Fatal error: Cannot redeclare is_rtl() (previously declared in /home/thethanks/www/www/wp-includes/locale.php:347) in /home/thethanks/www/www/wp-includes/locale.php on line 349

Can I manually install the update to 3.0.1 without logging into the Admin page?

Airohpue – You also have your own post https://www.ads-software.com/support/topic/we-have-a-piper-down?replies=3

Guys, this is part of why getting help can be frustrating. This topic should be for people who have a stalled upgrade. That is, one that does not finish. If your upgrade completed, but you have other errors, search for those errors on the site (or even on google, it helps), and if you can’t find it, make a new post. Don’t worry, we’ll find you. And probably faster than in this topic!