Using the auto update to 3.0.3 went smoothly. However, upgrading this time did not go so well. It failed.
Wait. It gets worse.
When it failed it left the message, “Under maintenance…” remained as the only thing a visitor to the site would see.
Downloaded 3.0.4 and upgraded manually. Now the site is back up, but the admin area still shows that the upgrade failed and suggest another go at it. If the link to take another go at upgrading is clicked it shows that the latest WP version is installed.
Is there a way to get the message at the top of the admin screen to show that the latest WP version is installed? It’s important to know when the updates are available.
Obviously ‘Make a backup first’ goes before anything…
It sounds like your bad upgrade got things stuck.
Go in via FTP and delete everything EXCEPT
wp-content (keep that WHOLE folder, do NOT touch it!)
Re-upload the 3.0.4 files
You WILL NOT hurt your settings or themes if you keep the files and folders I listed.
I logged into my page as Admin and clicked on the automatic update button. Everything appeared to be running normally until it locked up and I received a notice the update failed. When I tried to go back to my webpage my browser said it couldn’t find it. I tried using my FTP connection and it won’t let me in either. It was working so good until I updated it! Now it’s totally dead! I’ve already contacted my host, but they haven’t responded yet.
I tried using my FTP connection and it won’t let me in either.
Then you will have wait until your host checks it out as if you can not log in in ftp or server you can not do much
Call me a Nervous Nelly, but exporting the db is always my first course of action.
Using FTP and uploading the admin and includes files, plus the files in the root folder (sans the config file) removed the “Site under maintenance” message.
On another server the auto update worked fine.
Replace the files–except leave the wp-content file, wp-config.php alone and of course the .htaccess–as Ipstenu suggest. You can choose to delete or overwrite the files as I did.
Storyman – I think that’s a healthy attitude! 😉
The “Site under maintenance” message was due to having a file named ‘.maintenance’ in the root of your WP install. This is PART of why I said delete it all and copy up. That got set by the auto-updater and should clean itself out.
The real reason I say delete and re-copy is that some FTP clients are dumb, and sometimes the strudy tubes of the internet are clogged, and overwriting files just doesn’t work. So to cut out the middle man, delete 🙂
If you cannot log in through FTP, then you need to immediately contact your web host provider. They need to know because the program may be caught in a loop and slowing down the server’s CPU.
Two things I’d love to see happen with WordPress’s internal upgrade feature:
1) I’d love for it to work. Just once. I’ve never, EVER, been able to use the WP upgrade that’s been available since 2.7.
2) I’d love even more an easy way to find (fewer than two clicks please) exactly what files were updated and if a DB upgrade is necessary. To go through an entire upgrade over 10 files is overkill.
I use my FTP programs synchronization or comparison utility. Upload the necessary files, check if a DB upgrade is needed and Bob’s your Father’s Brother.
This upgrade thing must be a problem on server as when you update your host server needs to connect to wordpress server to get updated version must be having problem connecting.
I have updated all my plugins and updates without having any problem.
Heather – WordPress’ auto-upgrade works most of the time, which is pretty good. But. You’re right, it doesn’t work on all systems. Some don’t allow the php functions needed to run, and that’s not really WordPress’ fault, nor is there a huge amount they can do to fix it. It’s the nature of the beast.
As to your second problem, yes, the devs are actually working on a way to do smaller upgrades for security patches. Major point releases will still be a full copy, but this is something they’re aware of.
You can always find the files at http://codex.wordpress.org/Version_3.0.4 (where you change 3.0.4 to the version you’re upgrading to). On those pages, if the db_version changes, then there’s a DB Upgrade involved.
(And Bob’s my mother’s sister’s husband’s brother! Are we related? 😉 )
Yes, a DB update is necessary (this happens frequently with Drupal).
Unless you have a slew of WP sites upgrading more than 10 files should not be an issue. Upgrading a number of WP sites is a hassle if the auto update doesn’t work. It would be nice if they included a link to a page with which files are updated and if a db update is necessary. That way, those of us who find the auto update less than perfection would know what actually needs to be done.
Personally, I suspect it has more to do with the web hosting account because WP sites located with other hosting companies don’t have a problem. Maybe WP should run an upgrade test to see if the web hosting company is likely to play well with upgrade.
There’s no DB upgrade/update with 3.0.4 AFAIK… I don’t remember one at least!
And Storyman, yeah, but that would involve WordPress having an account on every webhost, on every variation of their servers. Not even the best webhost in the world has 100% exact copies of the same server for all their users. Not to mention plugins on your WordPress install can affect this. Too many variables. Otherwise you’d just get an error ‘can’t do this…’ Which is what you get.
Ipstenu wrote: “… that would involve WordPress having an account on every webhost…”
That’s a bit of overkill. What I’m suggesting is that after the FTP log in information is entered (as it is now) that before WP attempts an update that it run a test on each folder with a faux file making sure that it can download, unzip, and install the faux files. That should give the end user a pretty good idea if it is a good idea or not to continue with the full update.
Of course the ‘test’ should be optional. Those who already know that they can update without issue need not run it.
Didn’t see the DB update either, which leads me to believe that they were updating WP that was several versions back.
Maybe a better error message on the failure? I mean, if the install bombs out, no point in making it even longer for the successful people with an extra test.
Still, you already get an error message 🙂 Except when it just hangs like an old shoe. Which even a test wouldn’t fix.
I don’t know if this information is of any value towards finding a solution as to why the update failed on my host, but here goes… The http://www.ebookchronicles.com domain was my WordPress blog. I was using a really nice theme I downloaded for free from http://www.adazing.com. I was also running two subdomains under ebookchronicles. My subdomains were small in size and written in simple html format. My host tells me the files for my subdomains seem to have totally disappeared. They’re still working on ebookchronicles and trying to figure out why my FTP won’t let me log on. I can’t even start over from scratch until they get the FTP problem ironed out.
It may be a big fat poorly timed coincident, but the fact that you can’t get in via FTP is probably why the upload is barfing.
By the way, if you do the MANUAL upgrade, make sure you DO NOT delete any folders with the names of your subdomains 🙂
- The topic ‘Auto update to 3.04 issue’ is closed to new replies.