<?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: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>Mon, 02 Apr 2012 11:59:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-beta4-20725</generator>
	<item>
		<title>By: dem0crat</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-5/#comment-2014</link>
		<dc:creator>dem0crat</dc:creator>
		<pubDate>Sat, 01 May 2010 17:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-2014</guid>
		<description>Why does the threaded comments doesnt appear on its respective parent comment?</description>
		<content:encoded><![CDATA[<p>Why does the threaded comments doesnt appear on its respective parent comment?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reg</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-5/#comment-2007</link>
		<dc:creator>Reg</dc:creator>
		<pubDate>Mon, 26 Apr 2010 12:51:04 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-2007</guid>
		<description>Can anyone tell me how to get my blog&#039;s comment system to work like this blog&#039;s?
I&#039;ve tried IntenseDebate but it required Javascript which I don&#039;t want. It&#039;s also messy, where this blog&#039;s comment system is simple in it&#039;s layout.

My blog can&#039;t even get threaded comments. Any suggestions would be much appreciated.</description>
		<content:encoded><![CDATA[<p>Can anyone tell me how to get my blog&#8217;s comment system to work like this blog&#8217;s?<br />
I&#8217;ve tried IntenseDebate but it required Javascript which I don&#8217;t want. It&#8217;s also messy, where this blog&#8217;s comment system is simple in it&#8217;s layout.</p>
<p>My blog can&#8217;t even get threaded comments. Any suggestions would be much appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress Glossary &#187; wpMethod</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-5/#comment-2004</link>
		<dc:creator>WordPress Glossary &#187; wpMethod</dc:creator>
		<pubDate>Wed, 21 Apr 2010 14:14:02 +0000</pubDate>
		<guid isPermaLink="false">http://ottodestruct.com/blog/?p=424#comment-2004</guid>
		<description>[...] Comment Also commonly referred to as a reply, this is text that a reader submits in response to a post or page. They are then generally listed below the content of the post and page in order by date. The default settings will display them with the oldest comment first and then continue in ascending order, but this can be reversed in the discussion settings panel. You also have the option to paginate comments by only displaying a certain amount of comments per page. Additionally, you can turn on threaded commenting so that one can reply directly to another comment. The settings allow you to choose how many levels deep the thread can go. See more about threaded comments. [...]</description>
		<content:encoded><![CDATA[<p>[...] Comment Also commonly referred to as a reply, this is text that a reader submits in response to a post or page. They are then generally listed below the content of the post and page in order by date. The default settings will display them with the oldest comment first and then continue in ascending order, but this can be reversed in the discussion settings panel. You also have the option to paginate comments by only displaying a certain amount of comments per page. Additionally, you can turn on threaded commenting so that one can reply directly to another comment. The settings allow you to choose how many levels deep the thread can go. See more about threaded comments. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otto</title>
		<link>http://ottodestruct.com/blog/2008/wordpress-27-comments-enhancements/comment-page-4/#comment-1044</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-1044</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-5/#comment-1043</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-1043</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-4/#comment-1042</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-1042</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-5/#comment-1041</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-1041</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-5/#comment-1040</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-1040</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-5/#comment-1039</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-1039</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-5/#comment-1038</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-1038</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>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using xcache
Object Caching 450/484 objects using xcache

Served from: ottodestruct.com @ 2012-05-21 13:13:46 -->
