So WordPress 2.3 has just been released, and like I lot of people I uploaded and upgraded but then I reverted…
WordPress 2.3 changes over a lot of things in the back end like adding a native tagging system and removing some “older” elements, so the changes broke my archives (as neglected as they are) and, worst of all, broke my layout, legacy code I guess. Maybe I’m simple minded, but shouldn’t upgrades be, oh I dunno, painless? Or at least relatively?
Now bear in mind I’ve only used it for about 5 minutes, a couple of which was reuploading old files and restoring my SQL database, but I suggest you avoid this release. Why they decided to change the DB schema to cut off a great many things is beyond me, but I’ll stick with 2.2 for now… I suggest you do too, unless of course you use WP straight out the box with next to no plugins running and the default template.
I, on the other hand, am seriously looking for an alternative as I knew this would happen…
EDIT (28/9/07 9:12am): Since Dreamhost finally updated their one-click installer, I took a few hours last night and this morning to update to 2.3, it probably took around 3 hours in total to get things back up to speed…
Comments
8 responses to “WordPress 2.3 Thoughts”
you just seem angry at WP in general and looking for more reasons to move to something else.
personally, i enjoy doing WP upgrades. it’s fun to check out the guts and see how the schema changed or what new api tags are available to use. i look at it as a way to reevaluate my themes/plugins and make them better. like you point out, though, i don’t use a lot of plugins, so that makes it less headache-y.
I am so bad about this stuff. I haven’t changed or upgraded anything since I installed wordpress around November of last year. I guess I have a “if it ain’t broke” mentality. I just looked and I am running 2.0.5. Maybe I should upgrade to at least 2.2?
I dunno, I am a bit disillusioned with the running of WordPress and how the emphasis is on the .com while the .org is left to waste most of the time. And it’s all on the whims of the Automattic crew who, if you stand up and voice some concerns over un-needed elements, like say a half-cocked tagging system or WP “phoning home with some information about your set up, the reply 9/10 is “well, if you don’t like it, fork it.” I’ve complained about the support (or lack thereof) in the past, now it’s 10 times worse… I’d hate to be a new person coming to WordPress right now…
My main issue is the conversion of categories to tags, my layout relies heavily on categories to separate everything out and releasing something at 9/10pm meant I was just not in the mood to hunt down a tagging alternative to spitting out an id for styling purposes
And Duane, I would update to 2.2, if only for security reasons
.org does seem like the red headed stepchild to .com since it was launched. i’ve never complained directly to Automatic about anything, so I can’t comment on that, but i do agree that it does take a little know-how to get things accomplished when running your own WP install. i’m not sure that that’s not the nature of running your own blogging install, though. but, prior to WP i was using blogger, so what do i know? ;)
i don’t think that the tag update is meant to replace categories, though. you can choose to use tags or not. it’s just built-in now instead of using one of the various plugins.
Maybe I’ll give it another try over the weekend, but right now I’m in the “if it ain’t broke” train of thought.
Mind you, I wasn’t overly impressed with 2.0 back in the day either, the addition of that WYSIWYG interface and other things prolly signaled the beginning of the end in my eyes
Wow, I do sound like a bitter old man
bitter old man? nah. the WYSIWYG editor is a piece of crap, btw. thankfully it’s turnoffable.
i’ll probably wait until the weekend to upgrade, unless i get really bored some night.
Movable Type 4 can import from WordPress…
I finally said something that generated a response from THE Matt Mullenweg, I feel almost blessed…
I await said demonstration with baited breath