Or at least my little corner of it. I just upgraded to WordPress 2.3.1, and am getting some really cool errors up at the top of my page (just look up above, and you can see them for yourself).
I know what’s causing the problem, though: tagging. I’ve been using the Simple Tagging plugin for a while now, and apparently, it doesn’t play nicely with 2.3.1, because 2.3.1 comes with its own tag functionality built in. I suppose if I’d read up on the latest version of WordPress before upgrading, I would have known that. Alas, I like to live dangerously.
At any rate, I’m now left with a crappy selection of choices:
A. I can leave the error up above and continue to use Simple Tagging (basically not an option, because that error is pretty yuck, and I like things to work smoothly);
B. I can lose all of my tags that I’ve applied, and start over from scratch.
C. See below.
I know, there are some of you in the crowd going, “well, just import the tags from Simple Tagging, and then get rid of the plugin.” A fine idea - I’m just not sure that’s possible. It appears that Simple Tags is the successor to Simple Tagging; Simple Tags works with 2.3.1, and Simple Tagging does not. So, I’m now poking around, trying to figure out if there’s anyway for me to keep my tags, possibly by installing Simple Tags, importing my tags from Simple Tagging to Simple Tags, and then importing my tags from Simple Tags into the top-level, WordPress approved tags area.
Simple my ass.
So - if my system here explodes and you see bits of my blog floating around on the internet, you know what happened.
Update: All fixed. I wasn’t looking in the right area in WordPress for the tags importer. I found it; imported; and now all is well in the world - at least in my little digital corner of it.
P.S. WordPress makers: why, oh why, will you not make TinyMCE’s Full Screen function part of the standard offering on the editing window toolbar? Why?

7 comments
Comments feed for this article
Trackback link
http://system13.org/2007/11/04/i-broke-the-internet/trackback/
November 4, 2007 at 10:40 pm
Fig
Congratulations on getting it all figured out. I’m not seeing any errors at the moment.
By the way, whatever happened to “if it ain’t broke, don’t fix it?”
November 4, 2007 at 11:35 pm
Josh
Yeah, I got it fixed. I wasn’t looking in the right place for the importer. All is now well.
Regarding the expression… hah. Good question. Indeed, everything was fine with my WordPress install, and it did everything I needed. So why did I upgrade? Why, because 2.3.1 is the latest and greatest!
Or something.
November 5, 2007 at 2:24 am
Nils
Yuck. I’d been having these sudden visions again yesterday, of getting my act together and doing this stuff myself. You know, get hosting, coolio design and WP install.
Now I’m not so sure.
I can’t keep up with the internet and my feeds as it is, let alone fix it! I’ll stay with WP.com until I have some time. Until I’m dead probably.
All’s looking good indeed, though. Glad you sorted it out. Broken blogs are sad.
November 5, 2007 at 3:09 am
zhayena
You could use Simple Tags instead - it’s Simple Tagging for WP 2.3
What’s good with it is that you don’t have to edit your theme to make the tags show up, - unless you want to..
November 5, 2007 at 8:48 am
Josh
Nils: It’s not really that bad. Usually stuff works just fine. However, I’d be lying if I said that blogging with your own hosting is as simple as blogging at WP.com. I never had MySQL errors appear at WordPress.com.
Yeah, it’s all fixed now. However, things may change again very soon. I’m thinking about switching themes again, finally; I’ve grown tired of this one. I’m looking at Tarski (tarskitheme) for the next incarnation, which will hopefully be a little simpler than this version. In particular, over the past year, the sidebar has grown to unwieldy proportions.
Zhayena: That’s actually what I’m using now. It just took me a while to figure out how to get my tags from Simple Tagging to Simple Tags / WordPress 2.3.1.
It wasn’t simple. I want my money back.
November 5, 2007 at 10:40 pm
Edrei
Haha, you should have seen me the week I updated to WordPress 2.3. That was a nightmare to say the least. It wasn’t until later AFTER I smoothed everything out in my sandbox that I reattempted upgrading my WordPress again.
Going through 50+ plugins looking for the ones that are incompatible is a pain.
November 6, 2007 at 9:14 am
Josh
Edrei: Youch. That sounds like you had a lot more trouble than I did!
While I realize it’s probably a bit late, for “next time,” you might check out the WordPress Upgrade Preflight Check plugin:
Clicky.