Displaying posts tagged: wordpress
I will be participating in this year's Summer of Code, working on WordPress internationalization. You can read my full proposal online. Of over 6,000 applications, about 900 were accepted. WordPress could only accept 10 out of about 90 applications. It's bound to be an interesting summer with working on WordPress and Habari at the same time, plus $work, photography, and 'real' life....
Whee, the nice folks over at Watershed Studio have credited me for the stuff I contributed to the Sphere Related Content Plugin. :D
If you're using the latest bleeding-edge SVN version of WordPress with Ultimate Tag Warrior, check your feed's validity. WordPress is finally getting around to implementing Atom 1.0 instead of sticking with the comparatively ancient Atom 0.3 (even the validator's support is deprecated).
Unfortunately, due to the way WordPress and UTW work, UTW doesn't have a way to really know what kind of feed is requested -- the hook it registers is called the_category_rss, and it's called with a parameter that's either 'rdf', 'rss', and sometimes blank.
Even more unfortunate is that the_category_rss is called when an Atom feed is requested. UTW happily inserts the hardcoded <dc:subject> tags into the feed, and since that's been superseded by <category> in Atom 1.0, and WordPress doesn't declare the Dublin Core namespace anymore, your feed has just become invalid. Fix after the jump.
Update: The announcement is out. The important part is:...
In Changeset 4349, WordPress 2.1 lost the "jump to preview" / "jump to post" links. Aside from being damn useful, that changeset also broke the Kill Preview plugin....
Are Snap.com actually paying people a lot of money, or why would wordpress.com think it's a good idea to enable Snap Preview Anywhere on all wordpress.com blogs?
The add-meta-tags WordPress plugin broke my WordPress 2.1 alpha site in more ways than one.
Update: Version 0.7 is out with fixes.
Anyway, here's a (quick and dirty) patch against 0.6 to fix things.
{blog entries}
