WordPress 2.0 Sucks

i told myself i wouldn't upgrade my main blog. i told myself i was happy enough with the feature set of 1.5.2. since 2.0 fixed no security bugs, there was no reason to upgrade. especially after upgrading my test blog had gone so badly. (upgrading from 2.0 RC1).
but then i found out that squible beta 1 would be 2.0 only. i love squible, and i wanted the new features beta 1 promised. so i upgraded.

fortunately, i fared better this time. my upgrade actually took. but saying it worked would be quite a stretch. first thing to happen: none of my admin panels would open (except the dashboard). fortunately logging out and dumping the cache worked.

second thing i noticed: my feed stopped working. well, actually feedburner just says the root of the document is malformed. what's a blog without a feed? 1999.

thrid thing i noticed: squible is now spewing mySQL errors. ok, switch to another theme. k2 is spewing fewer errors. but there are no post pages. no, wait, all of my permalinks are broken. after a whole lot of futzing, i try editting the blog URI, because everything seems to be missing the 'index.php' section of the address.

now my blog's completely fucked. it can't read it's stylesheet, i can't use any of the admin pages, so i can't even fix the error. i try digging through phpMyAdmin, but i'm not an SQL expert, so i have no idea where to find or how to fix the blog URI value. as of writing, no one's responded on the support forums.

the thing that pisses me off is posts like this by wordpress team members, who make it seem like there's something wrong with you if you're not upgrading.

i ran a test blog, i ran the release candidates, but what was released barely resembled the release candidates. what was released was as stable as my ass after a couple burritos.

so as soon as i can, i'll be removing 2.0, reinstalling 1.5.2, and most likely having to wipe and re-import my database. (the downgrade script notwithstanding)(i think if i try the downgrade script i'll have the same blog URI issue with 1.5.2).


5 thoughts on “WordPress 2.0 Sucks

  1. Pingback: a laundry list of hand-wringing apologies » The Twilight Zone

  2. Big Duke

    Shit you’ve ruined my day now. I was just about to dive head first into WordPress. I’m new to this blogging bunkem and after spending 5 or 6 days with blogger I’ve had enough already. So it was WordPress or Moveable Type and I chose WordPress and now I’m going to have to start again because that sounds like more grief than I need and can handle. Is it the upgrade process that’s wrecked everything or is the release just pants! I’ve got to move on from blogger though, I’m pretty up to speed with the IT thing generally, web, db stuff, hardware and I never bothered venturing into blogs because I thought it trivial, as in for women and school kids, no offence. Wrong! This stuff is seriously technical and I’m out of breathe peddling to keep up. I don’t need software problems at the moment. I think I might go outside and meet someone for a chat, like I used to. Good luck anyway. Dave Nottingham, UK.

  3. Ben

    @Adam: I’ve said it before to you in our emails but I’ll say it again “on the record.” That totally sucks. I can’t imagine what happened that your blog borked so badly.

    @Big Duke: You may or may not have any problems installing WordPress 2.0. Most people, from what I’ve read have had no problems. The problems that Adam has had seem to be few and far between. As for choosing between Movable Type and WordPress I would definitely go with WordPress. I started out with blogger and then went to Movable Type. After a few months of headaches with MT I made the wise move to WordPress and have never looked back.

    @Adam (again): *sigh* man, that just sucks.

  4. sunburntkamel Post author

    big duke: fresh installs of wordpress 2.0 generally go smoothly, i’ve done 3-ish. my server is windows + IIS + mySQL + PHP. wordpress is designed for linux + Apache + mySQL + PHP.
    that said, there isn’t a customer support line to call. in the end, i only saved my own ass by doing a thorough backup beforehand.

Comments are closed.