<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" 
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: WordPress 2.7 Comments Enhancements</title>
	<atom:link href="http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/feed/" rel="self" type="application/rss+xml" />
	<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/</link>
	<description>Random meanderings you&#039;re probably not interested in</description>
	<lastBuildDate>Thu, 11 Mar 2010 06:10:23 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Genry</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6941</link>
		<dc:creator>Genry</dc:creator>
		<pubDate>Thu, 24 Sep 2009 10:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6941</guid>
		<description>I like it! thanks!</description>
		<content:encoded><![CDATA[<p>I like it! thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-6/#comment-6907</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Tue, 18 Aug 2009 17:06:22 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6907</guid>
		<description>No, there isn&#039;t. When the max depth is exceeded, get_comment_reply_link doesn&#039;t return anything. You&#039;d have to modify the get_comment_reply_link() function in comment-template.php.</description>
		<content:encoded><![CDATA[<p>No, there isn&#8217;t. When the max depth is exceeded, get_comment_reply_link doesn&#8217;t return anything. You&#8217;d have to modify the get_comment_reply_link() function in comment-template.php.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 8/18/2009: Weekly Links</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6906</link>
		<dc:creator>8/18/2009: Weekly Links</dc:creator>
		<pubDate>Tue, 18 Aug 2009 16:54:01 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6906</guid>
		<description>[...] Another resource for threaded comments. [...]</description>
		<content:encoded><![CDATA[<p>[...] Another resource for threaded comments. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kai</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-6/#comment-6905</link>
		<dc:creator>Kai</dc:creator>
		<pubDate>Mon, 17 Aug 2009 22:16:46 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6905</guid>
		<description>I&#039;m wondering if there was ever a solution found for Ben&#039;s questions re: adding &quot;comments won&#039;t nest below this level&quot; text on the final comment allowed in a nested sequence.</description>
		<content:encoded><![CDATA[<p>I&#8217;m wondering if there was ever a solution found for Ben&#8217;s questions re: adding &#8220;comments won&#8217;t nest below this level&#8221; text on the final comment allowed in a nested sequence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gavin</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6894</link>
		<dc:creator>gavin</dc:creator>
		<pubDate>Mon, 27 Jul 2009 21:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6894</guid>
		<description>Thanks, that last suggestion sounds sensible - and in effect gives a non-paging-dependent permalink for each comment. Where would such code go though? I&#039;ve not had much experience hacking  WP at this kind of level, so I may need to see if there is anyone out there that could be motivated to help out.</description>
		<content:encoded><![CDATA[<p>Thanks, that last suggestion sounds sensible &#8211; and in effect gives a non-paging-dependent permalink for each comment. Where would such code go though? I&#8217;ve not had much experience hacking  WP at this kind of level, so I may need to see if there is anyone out there that could be motivated to help out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6893</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Mon, 27 Jul 2009 20:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6893</guid>
		<description>Hmm. Should be possible to do with a plugin.

Essentially, the plugin would need to recognize the new URL, pull the comment ID value out of it there, then use the get_page_of_comment() function to find the page number to use. From there, you can do set_query_var(&#039;cpage&#039;, NNNN) to set the comments page to whatever the result it.

This would all have to happen before the query runs, meaning that you&#039;re not going to get nice bits like is_single() and so forth.

My suggestion would be to alter your links to look like /link/?comment=NNN instead. This avoids complexity, and you can just do something like $commment_id = (int) $_GET[&#039;comment&#039;] to safely get the comment id, without opening a security hole.</description>
		<content:encoded><![CDATA[<p>Hmm. Should be possible to do with a plugin.</p>
<p>Essentially, the plugin would need to recognize the new URL, pull the comment ID value out of it there, then use the get_page_of_comment() function to find the page number to use. From there, you can do set_query_var(&#8216;cpage&#8217;, NNNN) to set the comments page to whatever the result it.</p>
<p>This would all have to happen before the query runs, meaning that you&#8217;re not going to get nice bits like is_single() and so forth.</p>
<p>My suggestion would be to alter your links to look like /link/?comment=NNN instead. This avoids complexity, and you can just do something like $commment_id = (int) $_GET['comment'] to safely get the comment id, without opening a security hole.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gavin</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6892</link>
		<dc:creator>gavin</dc:creator>
		<pubDate>Mon, 27 Jul 2009 20:30:49 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6892</guid>
		<description>what about a more robust permalink structure for comments? i.e. that uses something like /2009/07/post-name/comment/123456/#comment-123456 and so is independent of any paging choices? That could get processed to always go to the correct page and the browser would still be able to find the name reference. I could go through the database making a change to the older links relatively automatically to allow for this. For reference, we have some 450 such links in our database and this would be more tractable than working out by hand what page of comments each of the old links are on.</description>
		<content:encoded><![CDATA[<p>what about a more robust permalink structure for comments? i.e. that uses something like /2009/07/post-name/comment/123456/#comment-123456 and so is independent of any paging choices? That could get processed to always go to the correct page and the browser would still be able to find the name reference. I could go through the database making a change to the older links relatively automatically to allow for this. For reference, we have some 450 such links in our database and this would be more tractable than working out by hand what page of comments each of the old links are on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6891</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Mon, 27 Jul 2009 19:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6891</guid>
		<description>Unfortunately, it&#039;s not that simple.

Everything after a hash mark in a URL literally doesn&#039;t get sent to the server. Hash marks indicate &quot;in-page&quot; links. When you have a URL that looks like example.com/link/morelink#hashtag then the only bit the server gets is &quot;GET /link/morelink&quot;. The browser then finds the hashtag in the page and auto-scrolls to it.

So WordPress never knows that you want to see comment-NNN, it just sees that you want the post. With links like that, it&#039;s impossible for WordPress to know you want a comment, because the browser never tells it that fact. And you can&#039;t even fix this with .htaccess, because the webserver itself (Apache) doesn&#039;t get the hashtag bit either.

So, the &lt;em&gt;only&lt;/em&gt; solution for leaving those old links working is to not have paging.</description>
		<content:encoded><![CDATA[<p>Unfortunately, it&#8217;s not that simple.</p>
<p>Everything after a hash mark in a URL literally doesn&#8217;t get sent to the server. Hash marks indicate &#8220;in-page&#8221; links. When you have a URL that looks like example.com/link/morelink#hashtag then the only bit the server gets is &#8220;GET /link/morelink&#8221;. The browser then finds the hashtag in the page and auto-scrolls to it.</p>
<p>So WordPress never knows that you want to see comment-NNN, it just sees that you want the post. With links like that, it&#8217;s impossible for WordPress to know you want a comment, because the browser never tells it that fact. And you can&#8217;t even fix this with .htaccess, because the webserver itself (Apache) doesn&#8217;t get the hashtag bit either.</p>
<p>So, the <em>only</em> solution for leaving those old links working is to not have paging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gavin</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6890</link>
		<dc:creator>gavin</dc:creator>
		<pubDate>Mon, 27 Jul 2009 18:49:34 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6890</guid>
		<description>ok, fair point about &#039;permanance&#039; - but the old comment link issue is a real problem. We need paging to reduce our page size, but we have 5 years worth of comments that include hundreds of links to previous comments - most of which are now broken. 

Is there perhaps a way to use a .haccess rule to morph a /#comment-NNN to a form which could be recognised by the server and the correct page calculation made within a plugin?</description>
		<content:encoded><![CDATA[<p>ok, fair point about &#8216;permanance&#8217; &#8211; but the old comment link issue is a real problem. We need paging to reduce our page size, but we have 5 years worth of comments that include hundreds of links to previous comments &#8211; most of which are now broken. </p>
<p>Is there perhaps a way to use a .haccess rule to morph a /#comment-NNN to a form which could be recognised by the server and the correct page calculation made within a plugin?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6889</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Mon, 27 Jul 2009 18:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6889</guid>
		<description>It&#039;s not actually possible to fix old comment links (other than turning off paging), because the links don&#039;t contain enough information to do that. Everything after the # is not sent to the server, so WP has no idea that you&#039;re wanting to see a specific comment there.

As for the other thing, hey, the blog owner can change anything on a whim, so they&#039;re as &quot;permanent&quot; as anything else.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not actually possible to fix old comment links (other than turning off paging), because the links don&#8217;t contain enough information to do that. Everything after the # is not sent to the server, so WP has no idea that you&#8217;re wanting to see a specific comment there.</p>
<p>As for the other thing, hey, the blog owner can change anything on a whim, so they&#8217;re as &#8220;permanent&#8221; as anything else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gavin</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6888</link>
		<dc:creator>gavin</dc:creator>
		<pubDate>Mon, 27 Jul 2009 17:57:25 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6888</guid>
		<description>not sure if this is a good place to ask this, but I&#039;m having a big problem with the comment permalinks. Old permalinks (from pre WP2.7) no longer work with paged comments (since they are missing a /comment-page-N/ segment, so that is a pain. But more importantly, the new permalinks aren&#039;t in fact permalinks at all. They are completely dependent on how many comments there are per page - which can change at a blog-owners whim. Does anyone have a solution to fixing the old comment links? (which in fact would solve the permalink problem in it&#039;s entirety since the new permalink form could be scrapped completely).</description>
		<content:encoded><![CDATA[<p>not sure if this is a good place to ask this, but I&#8217;m having a big problem with the comment permalinks. Old permalinks (from pre WP2.7) no longer work with paged comments (since they are missing a /comment-page-N/ segment, so that is a pain. But more importantly, the new permalinks aren&#8217;t in fact permalinks at all. They are completely dependent on how many comments there are per page &#8211; which can change at a blog-owners whim. Does anyone have a solution to fixing the old comment links? (which in fact would solve the permalink problem in it&#8217;s entirety since the new permalink form could be scrapped completely).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paintbits &#187; Blog Archive &#187; Lumen Reborn is here&#8230;</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6884</link>
		<dc:creator>Paintbits &#187; Blog Archive &#187; Lumen Reborn is here&#8230;</dc:creator>
		<pubDate>Mon, 27 Jul 2009 00:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6884</guid>
		<description>[...] that the part that gave me the most trouble was the comment section. I tought in doing the comments a la Wordpress 2.7 style (that is, threaded, paged&#8230;) but I find threaded comments a bit combersume, so I decided to [...]</description>
		<content:encoded><![CDATA[<p>[...] that the part that gave me the most trouble was the comment section. I tought in doing the comments a la Wordpress 2.7 style (that is, threaded, paged&#8230;) but I find threaded comments a bit combersume, so I decided to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mastering Your WordPress 2.7 Theme &#38; Admin Area: Tips and Tricks &#124; Webmaster Zone - Cyooh.com</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6880</link>
		<dc:creator>Mastering Your WordPress 2.7 Theme &#38; Admin Area: Tips and Tricks &#124; Webmaster Zone - Cyooh.com</dc:creator>
		<pubDate>Thu, 23 Jul 2009 00:32:40 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6880</guid>
		<description>[...] comments compatible with WordPress 2.7 should be your first step when you edit your theme files. Otto has written a detailed post on the new comment enhancements in WordPress [...]</description>
		<content:encoded><![CDATA[<p>[...] comments compatible with WordPress 2.7 should be your first step when you edit your theme files. Otto has written a detailed post on the new comment enhancements in WordPress [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress 2.7 &#8220;Coltrane&#8221; Now Available! &#124; Swank Web Style Blog</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6878</link>
		<dc:creator>WordPress 2.7 &#8220;Coltrane&#8221; Now Available! &#124; Swank Web Style Blog</dc:creator>
		<pubDate>Mon, 20 Jul 2009 19:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6878</guid>
		<description>[...] How to Create a 2.7 Compatible Comments.php [...]</description>
		<content:encoded><![CDATA[<p>[...] How to Create a 2.7 Compatible Comments.php [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-2/#comment-6877</link>
		<dc:creator>Otto</dc:creator>
		<pubDate>Mon, 20 Jul 2009 13:18:16 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6877</guid>
		<description>Avatars are included in the wp_list_comments, you don&#039;t need to call them manually. Just turn them on in the Settings-&gt;Discussion screen.</description>
		<content:encoded><![CDATA[<p>Avatars are included in the wp_list_comments, you don&#8217;t need to call them manually. Just turn them on in the Settings->Discussion screen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: manju</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-2/#comment-6876</link>
		<dc:creator>manju</dc:creator>
		<pubDate>Mon, 20 Jul 2009 10:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6876</guid>
		<description>How is Gravatar support enabled in the new comments loop? I currently have this piece of code:
echo get_avatar( get_comment_author_email blah blah</description>
		<content:encoded><![CDATA[<p>How is Gravatar support enabled in the new comments loop? I currently have this piece of code:<br />
echo get_avatar( get_comment_author_email blah blah</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Making of a Monsta &#8230; WordPress Theme &#124; Jeremy Adam Davis</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6874</link>
		<dc:creator>The Making of a Monsta &#8230; WordPress Theme &#124; Jeremy Adam Davis</dc:creator>
		<pubDate>Fri, 17 Jul 2009 05:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6874</guid>
		<description>[...] Another hurdle was getting comments to thread properly. Here’s how to get threaded comments in WordPress. [...]</description>
		<content:encoded><![CDATA[<p>[...] Another hurdle was getting comments to thread properly. Here’s how to get threaded comments in WordPress. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Building Wordpress Themes &#8211; Part 12 &#171; A Path Less Taken</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6873</link>
		<dc:creator>Building Wordpress Themes &#8211; Part 12 &#171; A Path Less Taken</dc:creator>
		<pubDate>Thu, 16 Jul 2009 03:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6873</guid>
		<description>[...] http://ottodestruct.com/blog/2008/09/29/wordpress-27-comments-enhancements &#8211; Otto’s post here is the inspiration for a substantial help document on the Wordpress.org site related to the new comments loop. His demonstration of background color formatting for different classes of comments inspired me to take a similar approach to identify pingbacks and tracebacks. I also wanted a different background color for comments made by me on my own blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://ottodestruct.com/blog/2008/09/29/wordpress-27-comments-enhancements" rel="nofollow">http://ottodestruct.com/blog/2.....hancements</a> &#8211; Otto’s post here is the inspiration for a substantial help document on the Wordpress.org site related to the new comments loop. His demonstration of background color formatting for different classes of comments inspired me to take a similar approach to identify pingbacks and tracebacks. I also wanted a different background color for comments made by me on my own blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jessica Sideways</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-1/#comment-6872</link>
		<dc:creator>Jessica Sideways</dc:creator>
		<pubDate>Tue, 14 Jul 2009 11:11:28 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6872</guid>
		<description>That&#039;s good because I was worried this new &quot;featured&quot; would fuck up my theme that I am working on.</description>
		<content:encoded><![CDATA[<p>That&#8217;s good because I was worried this new &#8220;featured&#8221; would fuck up my theme that I am working on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allpa</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-1/#comment-6871</link>
		<dc:creator>Allpa</dc:creator>
		<pubDate>Tue, 14 Jul 2009 00:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6871</guid>
		<description>I ask to forgive my poor English - I live in Ukraine, I use the program-compiler: (

At me all has turned out, except one - comments turn out NOT threaded though the necessary point in options WP is noted.

And it just what I try to achieve from comments in a blog http://allpa.ru/- what to do? How to rectify situation? 
Very much I hope for your help...

It would be desirable to allocate still comments of the author of a blog with other colour how it is made at you - you could not prompt the necessary actions?

Thanks!:)</description>
		<content:encoded><![CDATA[<p>I ask to forgive my poor English &#8211; I live in Ukraine, I use the program-compiler: (</p>
<p>At me all has turned out, except one &#8211; comments turn out NOT threaded though the necessary point in options WP is noted.</p>
<p>And it just what I try to achieve from comments in a blog <a href="http://allpa.ru/-" rel="nofollow">http://allpa.ru/-</a> what to do? How to rectify situation?<br />
Very much I hope for your help&#8230;</p>
<p>It would be desirable to allocate still comments of the author of a blog with other colour how it is made at you &#8211; you could not prompt the necessary actions?</p>
<p>Thanks!:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6868</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Fri, 03 Jul 2009 23:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6868</guid>
		<description>Good rundown on changes.  Very helpful.</description>
		<content:encoded><![CDATA[<p>Good rundown on changes.  Very helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress 2.7 Comments Enhancements</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6867</link>
		<dc:creator>WordPress 2.7 Comments Enhancements</dc:creator>
		<pubDate>Thu, 02 Jul 2009 19:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6867</guid>
		<description>[...] posted here: WordPress 2.7 Comments Enhancements      Tags:     Comments0  Leave a Reply  Click here to cancel [...]</description>
		<content:encoded><![CDATA[<p>[...] posted here: WordPress 2.7 Comments Enhancements      Tags:     Comments0  Leave a Reply  Click here to cancel [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress 2.7 Comments Enhancements &#124; WordPress News - New WordPress Themes</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6866</link>
		<dc:creator>WordPress 2.7 Comments Enhancements &#124; WordPress News - New WordPress Themes</dc:creator>
		<pubDate>Sun, 28 Jun 2009 21:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6866</guid>
		<description>[...] WordPress 2.7 Comments Enhancements   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress 2.7 Comments Enhancements   Share and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mastering Your WordPress 2.7 Theme &#38; Admin Area: Tips and Tricks &#124; Quest For News, A TUTORIAL Base</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6865</link>
		<dc:creator>Mastering Your WordPress 2.7 Theme &#38; Admin Area: Tips and Tricks &#124; Quest For News, A TUTORIAL Base</dc:creator>
		<pubDate>Sat, 27 Jun 2009 16:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6865</guid>
		<description>[...] comments compatible with WordPress 2.7 should be your first step when you edit your theme files. Otto has written a detailed post on the new comment enhancements in WordPress [...]</description>
		<content:encoded><![CDATA[<p>[...] comments compatible with WordPress 2.7 should be your first step when you edit your theme files. Otto has written a detailed post on the new comment enhancements in WordPress [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Separating and Hiding Trackbacks with Jquery in WordPress 2.7 &#124; Quest For News, A TUTORIAL Base</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6863</link>
		<dc:creator>Separating and Hiding Trackbacks with Jquery in WordPress 2.7 &#124; Quest For News, A TUTORIAL Base</dc:creator>
		<pubDate>Sat, 27 Jun 2009 16:33:50 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6863</guid>
		<description>[...] in the ol&#8217; comment file in Wordpress 2.7. I highly suggest taking a peek at Otto&#8217;s WordPress 2.7 Comments Enhancements if you haven&#8217;t already. He outlines how the new comment loop works, and all the spiffy [...]</description>
		<content:encoded><![CDATA[<p>[...] in the ol&#8217; comment file in Wordpress 2.7. I highly suggest taking a peek at Otto&#8217;s WordPress 2.7 Comments Enhancements if you haven&#8217;t already. He outlines how the new comment loop works, and all the spiffy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Separating and Hiding Trackbacks with Jquery in WordPress 2.7 &#124; Quest For News, A TUTORIAL Base</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6864</link>
		<dc:creator>Separating and Hiding Trackbacks with Jquery in WordPress 2.7 &#124; Quest For News, A TUTORIAL Base</dc:creator>
		<pubDate>Sat, 27 Jun 2009 16:33:50 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6864</guid>
		<description>[...] in the ol&#8217; comment file in Wordpress 2.7. I highly suggest taking a peek at Otto&#8217;s WordPress 2.7 Comments Enhancements if you haven&#8217;t already. He outlines how the new comment loop works, and all the spiffy [...]</description>
		<content:encoded><![CDATA[<p>[...] in the ol&#8217; comment file in Wordpress 2.7. I highly suggest taking a peek at Otto&#8217;s WordPress 2.7 Comments Enhancements if you haven&#8217;t already. He outlines how the new comment loop works, and all the spiffy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weiße / Leere Seite nach Kommentar – Wordpress - - ITler.NET - Der Blog für ITler und Sysadmins</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6861</link>
		<dc:creator>Weiße / Leere Seite nach Kommentar – Wordpress - - ITler.NET - Der Blog für ITler und Sysadmins</dc:creator>
		<pubDate>Sat, 20 Jun 2009 13:01:38 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6861</guid>
		<description>[...] Erweiterte Kommentar-Funktionalität ab Wordpress-Version 2.7 (siehe auch Wordpress-Info) Stimmen die Einstellungen nicht überein, kann es zu diesem Problem [...]</description>
		<content:encoded><![CDATA[<p>[...] Erweiterte Kommentar-Funktionalität ab Wordpress-Version 2.7 (siehe auch Wordpress-Info) Stimmen die Einstellungen nicht überein, kann es zu diesem Problem [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bold Feature Rundown &#187; random process &#124; charlie 2.0</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6860</link>
		<dc:creator>Bold Feature Rundown &#187; random process &#124; charlie 2.0</dc:creator>
		<pubDate>Fri, 19 Jun 2009 02:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6860</guid>
		<description>[...] the way I wanted. I&#8217;m planning on writing a few tidbits for others in the same position. Even Otto&#8217;s excellent post didn&#8217;t quite do [...]</description>
		<content:encoded><![CDATA[<p>[...] the way I wanted. I&#8217;m planning on writing a few tidbits for others in the same position. Even Otto&#8217;s excellent post didn&#8217;t quite do [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nate</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6858</link>
		<dc:creator>nate</dc:creator>
		<pubDate>Mon, 15 Jun 2009 05:14:12 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6858</guid>
		<description>Thank you thank you thank you Otto.

All the hours I wasted with IntenseDebate can now be redeemed by Wordpress&#039; genius integration of these new comment enhancements. Not only is it completely functional, but I can make it look cool too.</description>
		<content:encoded><![CDATA[<p>Thank you thank you thank you Otto.</p>
<p>All the hours I wasted with IntenseDebate can now be redeemed by Wordpress&#8217; genius integration of these new comment enhancements. Not only is it completely functional, but I can make it look cool too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-04-22 .:: [aka щямукюшт] Ozver.in &#124; Озверин</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-8/#comment-6857</link>
		<dc:creator>links for 2009-04-22 .:: [aka щямукюшт] Ozver.in &#124; Озверин</dc:creator>
		<pubDate>Sun, 14 Jun 2009 16:33:30 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-6857</guid>
		<description>[...] WordPress 2.7 Comments Enhancements (tags: wordpress comments themes tutorial theme tutorials tips howto wordpress-2.7) [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress 2.7 Comments Enhancements (tags: wordpress comments themes tutorial theme tutorials tips howto wordpress-2.7) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
