Looks like WordPress 2.6 is out. I submitted three patches about three months ago: 6583, 6602 and 6642. I'd like to sturdy up WordPress's ability to handle invalid XHTML markup. Care to take a whack at my XHTML Piñata? This all sounds vaguely familiar.
Anyway does anyone have any suggestions on how to get these patches moving? Someone I need to email? kthxbai
I spent some time a few weeks ago quietly trying to shore up my XHTML defenses on my WordPress install - not everyone is planning to move to Drupal just yet. I have a bunch of patches that are aging. I think three of them are 'good to go' but I need someone to look at them. The patch for Ticket 5998 needs some work to make it applicable across trackbacks and pingbacks as well as ensuring it is applicable only for UTF-8. Unfortunately, no one is really looking at the patches because apparently no one on this planet would bother serving WordPress as true XHTML. Anyway, enough whinging - it would be great if some of these could make it into WordPress 2.5.1.
In the meantime, if anyone wants to try and break my WordPress install by injecting funky XHTML, please be my guest on this page. Currently Sam is in the lead with two breakages (now fixed). Oh, and your name doesn't have to be Philip, Jacques, Mark or Shelley either.
I think XHTMLate should be pronounced "stimulate". Anyway, here's a list of WordPress bugs that I think are important for XHTML: Read the rest of this entry ...
Sander asked me to post a list of bugs that I found as a result of working on my new theme. Here they are. Read the rest of this entry ...