Ketwaroo

the only good thing is that we can start making out some pattern in recent wordpress upgrades. The next major(or even minor) version will <b>always</b> remove something of the previous version that quite a lot of people found to be immensely valuable and add something “new and exciting” that will very likely piss off many long time users.

sorry, my post isn’t very relevant to the current direction of this thread but I’m in a particularly good mood thinking of a friend of mine who is an upgrade fanatic and upgraded to wp2.5 as soon as it came out and how he must be suffering all the woes of the earth with the new posting interface.

myself I only just downloaded the new 2.5.1 version and have been tinkering it on my local machine(wamp, localhost, that sort of thing).

I don’t supposed we could just take the security fixed files in 2.5 and copy them to a 2.3.3 installation and trim them up a bit to fit? I mean as far as the minutes of the changelog tell us, its mostly to do with the XML RPC thingy and stuff with registrations.

Hurray! but that still doesn’t solve this problem:

<i class="foobar">foo bar</i>

gets edited to

<i>foo bar</i>

really really really annoying. can’t use inline styles(excapt on span and div), can’t use javascript, can’t use anything that would have made posts and pages more interesting.

If it were to prevent anything funny in the comments, i would’ve understood. but why do it for posts. Trust the blogger to know what he/she is doing will ya?
and even if it isn’t valid xhtml, let em take the risk. It’s their blog after all.

that said, it there an option to disable that undue html chaperonage?

if there isn’t, what files/functions/piece of code can i cannibalise from wp2.0 and reuse in my wp2.1 installation. or is there a plugin that can disable all those unwanted features and make wordpress behave like the blogger dictates and not the other way around?