Five six posts in five in six days. I need to take a break. Not because I’m tired or am running out of things to say, but I need to do some serious housekeeping on the blog here. It’s a little technical, but WordPress users and interested geeks should keep reading.
I love WordPress. I can’t imagine switching to any other publishing engine, unless I build one myself sometime . (Yeah, right). But WP has a serious problem: Neither of its Textile plug-ins work.
Jim Rigg’s plugin hasn’t had any new development for a long time. It works decently for most of the stuff I want it to do, but lately, with the newest version of WP, is wrecking havoc with my paragraphs, line breaks, and blockquotes, and even editing in HTML doesn’t fix it as long as the plugin is enabled. Since it’s based on Brad Choate’s excellent version of Textile for Movable Type, which I used for well over a year, its features are what I think of when I think of Textile.
Then there’s Joel Bennett’s excellent TextileWrapper for WP. Although this was updated and released just a few days ago, It’s even less acceptable to me. Bennett says that this truly is Dean Allen’s Textile for WP, no core code or features changed at all. Perhaps it does work just like that for Textpattern, but that doesn’t seem to be happening, and if it is the case, it’s Choate-style Textile I need.
For instance, one of the things I found most convenient about Choate’s Textile, is how easy it was to add a class to virtually any element, without going into the HTML. I use a class for indicating which links are external and producing a little “offsite” symbol, for instance. Not only is that not working in this build of of WP and Bennett’s release, but it doesn’t insert classes for a tags, inline styles for anything that I can tell, and freaks out when Textile markup is nested within other markup.
I have but one solution: Get rid of all the Textile markup, since I don’t know how any future release of WP or ported-over versions of Textile will play with together. This will not be fun. I have over two hundred 230 posts now, probably 160 or so with Textile code. But I need to do this now before it gets worse.
2 thoughts on “Whew. Time for a break”
Wait, how’d I manage to comment on the wrong one. I could swear I clicked this link!
Or. Instead of abandoning it, hack the code up to work like you want it to work 🙂 . I think your ready for that!
I’ve tried. And far better PHP coders than I have tried.
I read something, somewhere, last night that one problem is with the order in which the WP processing works. Even if the perfect adjustments are made for Textile to work with WP now, they are probably not future-proof. Removing Textile markup is.