James’s Musings

thoughts, photography, and geeky stuff
from an unrelentingly curious Silicon Valley entrepreneur

Back on the Air – FINALLY!

by James G. Beldock on April 26, 2008

For the past few weeks, I’ve been at the mer­cy of an un­for­tu­nate bug in the ini­tial re­lease of WordPress 2.5 (specif­i­cal­ly, the 2.5.0 re­lease) which ren­dered me ut­ter­ly un­able to post. Proving on­ce again that one should nev­er trust the dot-ze­ro re­lease of any soft­ware pro­duct, I strug­gled through three weeks of sup­port fo­rum post­ings on­ly to find that, in the end, WordPress need­ed to fix the prob­lem them­selves. (For those in­ter­est­ed in the techy de­tails: some­thing in WordPress 2.5.0 broke a sin­gle line of JavaScript in TinyMCE, the rich text ed­i­tor used by WordPress for cre­at­ing posts. And, no, this is not the you-need-to-turn-on-the-vi­su­al-ed­i­tor “bug” which a few peo­ple were fooled by.) Fortunately, the 2.5.1 re­lease is out, and among oth­er things it pro­vides an up­grad­ed ver­sion of the cul­prit com­po­nent. (TinyMCE is now at 3.0.7; the 3.x fam­i­ly, ini­tial­ly in­tro­duced in WordPress 2.5.0, is sub­stan­tial­ly up­grad­ed from the 2.x se­ries on which WordPress used to re­ly.) For those who re­ly on Andrew Ozz’s very use­ful TinyMCE Advanced plug-in, you’ll want to down­load the 3.0.1.version which is com­pat­i­ble with WordPress 2.5.1 and TinyMCE 3.0.7. It al­so adds an in­cred­i­bly use­ful new fea­ture: fi­nal­ly, it al­lows you to con­trol whether TinyMCE au­to­mat­i­cal­ly tries to re­move <P> and <BR> tags when sav­ing. (Here’s a hint: if I want­ed it to do that, I’d tell it to do that!)

So, we’re back on the air. Stay tuned….

Be Sociable, Share!

Comments on this entry are closed.

Previous post:

Next post: