<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Safe Title: a WordPress plugin</title>
	<atom:link href="http://www.thunderguy.com/semicolon/2005/06/17/safe-title-wordpress-plugin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thunderguy.com/semicolon/2005/06/17/safe-title-wordpress-plugin/</link>
	<description>Software, the Internet and you.</description>
	<pubDate>Fri, 29 Aug 2008 06:26:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Bennett</title>
		<link>http://www.thunderguy.com/semicolon/2005/06/17/safe-title-wordpress-plugin/#comment-37</link>
		<dc:creator>Bennett</dc:creator>
		<pubDate>Fri, 01 Jul 2005 03:20:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.thunderguy.com/semicolon/?p=56#comment-37</guid>
		<description>Writing this plugin was a useful exercise for many reasons. I've discovered a few bugs in WordPress:

1. "the_title" filters are called with varying argument. Sometimes called with just the title as argument, sometimes with a post object, and sometimes with the title and the before and after strings. Safe Title expects three args, so frequently doesn't work properly because of this WordPress bug.

2. In function next_post(), calls the "the_title" filters with a nonexistent $nextpost variable. It should be $post.

Note to self: submit a patch to WordPress core.</description>
		<content:encoded><![CDATA[<p>Writing this plugin was a useful exercise for many reasons. I&#8217;ve discovered a few bugs in WordPress:</p>
<p>1. &#8220;the_title&#8221; filters are called with varying argument. Sometimes called with just the title as argument, sometimes with a post object, and sometimes with the title and the before and after strings. Safe Title expects three args, so frequently doesn&#8217;t work properly because of this WordPress bug.</p>
<p>2. In function next_post(), calls the &#8220;the_title&#8221; filters with a nonexistent $nextpost variable. It should be $post.</p>
<p>Note to self: submit a patch to WordPress core.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mathias Bynens</title>
		<link>http://www.thunderguy.com/semicolon/2005/06/17/safe-title-wordpress-plugin/#comment-28</link>
		<dc:creator>Mathias Bynens</dc:creator>
		<pubDate>Fri, 17 Jun 2005 12:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.thunderguy.com/semicolon/?p=56#comment-28</guid>
		<description>Nice, you made a plugin for it! However, output buffering sucks. Performing such heavy operations before sending out a page makes me wonder if it's actually better to leave the HTML out of the title at all! Not to bash your plugin, not at all --- &lt;strong&gt;it rawks!&lt;/strong&gt; --- but it's just so silly WordPress hasn't got this implemented. I hope the dev team soon applies &lt;a href="http://trac.wordpress.org/ticket/1371" rel="nofollow"&gt;my patch&lt;/a&gt;, so people won't have to hack their way or use plugins in order to be able to embed HTML into post titles.</description>
		<content:encoded><![CDATA[<p>Nice, you made a plugin for it! However, output buffering sucks. Performing such heavy operations before sending out a page makes me wonder if it&#8217;s actually better to leave the HTML out of the title at all! Not to bash your plugin, not at all &#8212; <strong>it rawks!</strong> &#8212; but it&#8217;s just so silly WordPress hasn&#8217;t got this implemented. I hope the dev team soon applies <a href="http://trac.wordpress.org/ticket/1371" rel="nofollow">my patch</a>, so people won&#8217;t have to hack their way or use plugins in order to be able to embed HTML into post titles.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
