Try:
– switching to the Twenty Twelve theme by renaming your current theme’s folder inside wp-content/themes and adding “-old” to the end of the folder name using FTP or whatever file management application your host provides.
– resetting the plugins folder by FTP or phpMyAdmin.
– re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.
– running the upgrade manually via wp-admin/upgrade.php
Thanks. Yikes, so much for one click upgrade, I might leave that for when I really need to upgrade! I assume after the steps you outline I could then revert to my theme of choice.
I will definitely pass on this upgrade then. How come 3.5 has broken stuff?
The only real things that are “broken” are incompatible plugins and themes and there’s not a lot we can do about them. Plugin & theme authors have had months to test their products against 3.5 whilst it was still in beta but, sadly, some don’t bother.
The only other real issues are:
– a known bug with HTML in scheduled Posts
– some servers can’t handle minified or concatenated javascript but this is very much host/server specific.
– one issue that effects some Windows servers only.
Thanks for that. Do I gather from that then that it’s the theme I am using which is the problem?
Nope. That looks like the core upgrade didn’t complete correctly. It does happen sometimes with auto-upgrades. All it needs is for one of the 2 servers involved to hiccup. what you definitely need to do is re-upload all of the core files & folders (except for the wp-content folder). Switching themes and turning off all plugins is recommended to both:
– ensure that nothing slows down or blocks the upgrade
– avoid the site falling down post-upgrade (and locking you out) because of an incompatible theme or plugin
Yikes. I think I’ll be waiting for a patch fix before I try anything else.
There’s no patch for this. I think it was just one of those 1 in a million hiccups.
1 in a million. So I am the only user who upgrade path is broken by 3.5?
The steps outlined are too risky for me to risk loosing my whole site but I would like to stay current 🙁
Too risky? Your site’s content is in your database – not in any files.
Well the site revolves around my chosen tweaked theme and you suggested it was not definite that 3.5 would work with it after the complex upgrade steps outlined above.
If you do not keep WordPress up-to-date, then your site runs the very real risk of being hacked.
Completely. That’s why I am hoping for a patch for the broken upgrade path. Where can I report the bug?
At the least wordpress should release a set of definite instruction for that will definitely work for this bug they have introduced.
What bug are you referring to? This issue is specific to your site and is almost certainly caused by a corrupt WordPress core file. It is not a core bug.
