My posting habbits lately suck. To all the complainers: bite me.
This weekend I thought it would be nice to work on a fresh theme and dig into WordPress 2.0.x. Kubrick seems to do everything it can to make any customization non-trivial. For example, trying to change the colors. In the Stylesheet, font and color styles get their own section at the top. Nice, right? Until you discover that the same tags are defined again later in the Stylesheet, WITH COLORS! For an hour or two I thought that I was freakin’ crazy. Thank God for Firefox’s DOM Inspector or I probably would have blown my brains out already over that. Kubrick does lots of other stupid-ass things too, like defining styles outside of the Stylesheet. I know there’s a movement to kill Kubrick as the default WordPress theme, I just hope that whatever is chosen as a replacement actually embodies the best practices of theme design instead of merely being pretty and cool.
But enough about Kubrick.
I’ve also discovered that WordPress’s TinyMCE support has some sort of double-decoding bug. If I post the following, with or without TinyMCE enabled:
<code />
<code>test</code>
When I edit that entry with TinyMCE turned on I get this:
<code />
test
And if I post something like this:
<blah>blah blah blah</blah>
It actually strips the <blah> tags when I edit it in TinyMCE!
Or how about if I type:
&
I get back:
&
And for extra fun, even tho WordPress doesn’t do WYSIWYG in Safari, it will still mess your stuff up if you have the option turned on.
I’m guessing that they were trying to “do the right thing” when HTML gets entered into the WYSIWYG control, but in the end they’ve done a much worse thing — what you save isn’t necessarily what you get back.
Note: None of the WYSIWYG complaints above will make any sense if you’re reading this in an RSS reader that double-decodes.
