Did you upgrade in “steps” – that is, from 1.22 (or whatever) to 1.5, then to 2.0+? If not, the database may not have got itself into proper shape.
Nope.
Straight from 1.5 (I think) to the latest incarnation (2.3, is it now?).
How would one get their database back into shape?
Yoga?
Pilates?
Okay, if you started with 1.5, then there shouldn’t be a problem. For some reason the way you phrased your post I thought earlier than 1.5.
So your database shouldn’t be problematic. And in fact, I’ve done a dozen or so 1.5+ to 2.0.3 upgrades just in the last week or so, and haven’t seen the error (and yes, TRULY unhelpful!) you describe.
But that error…. that’s almost more like a host notification error. Have you thought to ask your host support about it just in case?
Out of curiousity (and desire for learning) this is what I always do with error messages:
http://www.google.ca/search?q=HTTP+status+code+was+not+200
The results (almost) always can point you to:
– the server/host
– the script or
– whatever is to blame 🙂
Yeah, I already did that, but all I could figure out is that a 200 means everything’s ok, so the code not being 200 would mean that everything’s NOT ok. Real helpful.
Although last time I googled I didn’t notice the WordPress links for some reason.
Could this problem be caused by not deleting files properly?
Ugh, I don’t want to go through the whole upload process again.
OK!
I totally just figured out what this is.
My Livejournal crossposter Plugin is definitely not compatable with the new upgrade.
Wow. I’m glad that’s such a simple fix.
