<?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/"
		>
<channel>
	<title>Comments on: Enhance WordPress wp_list_authors Template Tag</title>
	<atom:link href="http://www.takaitra.com/posts/234/feed" rel="self" type="application/rss+xml" />
	<link>http://www.takaitra.com/posts/234</link>
	<description>life, ruminations, how-to's</description>
	<lastBuildDate>Thu, 22 Jul 2010 16:46:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: FlossieT</title>
		<link>http://www.takaitra.com/posts/234/comment-page-1#comment-2234</link>
		<dc:creator>FlossieT</dc:creator>
		<pubDate>Wed, 24 Mar 2010 22:53:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.takaitra.com/?p=234#comment-2234</guid>
		<description>&lt;a href=&quot;#comment-2207&quot; rel=&quot;nofollow&quot;&gt;@Takaitra&lt;/a&gt; 
Absolutely - it was just what I was looking for, and I&#039;ve also used it to improve a sidebar plugin. Now I just need to figure out how to patch your sorting even further to randomise the listing of authors...</description>
		<content:encoded><![CDATA[<p><a href="#comment-2207" rel="nofollow">@Takaitra</a><br />
Absolutely &#8211; it was just what I was looking for, and I&#8217;ve also used it to improve a sidebar plugin. Now I just need to figure out how to patch your sorting even further to randomise the listing of authors&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Takaitra</title>
		<link>http://www.takaitra.com/posts/234/comment-page-1#comment-2207</link>
		<dc:creator>Takaitra</dc:creator>
		<pubDate>Fri, 26 Feb 2010 04:14:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.takaitra.com/?p=234#comment-2207</guid>
		<description>Great, I&#039;m glad you were able to apply the patch.</description>
		<content:encoded><![CDATA[<p>Great, I&#8217;m glad you were able to apply the patch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FlossieT</title>
		<link>http://www.takaitra.com/posts/234/comment-page-1#comment-2205</link>
		<dc:creator>FlossieT</dc:creator>
		<pubDate>Thu, 25 Feb 2010 12:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.takaitra.com/?p=234#comment-2205</guid>
		<description>&lt;a href=&quot;#comment-2204&quot; rel=&quot;nofollow&quot;&gt;@FlossieT&lt;/a&gt; 
Ignore me - figured it out. Doh! FANTASTIC stuff. Exactly what I needed.</description>
		<content:encoded><![CDATA[<p><a href="#comment-2204" rel="nofollow">@FlossieT</a><br />
Ignore me &#8211; figured it out. Doh! FANTASTIC stuff. Exactly what I needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FlossieT</title>
		<link>http://www.takaitra.com/posts/234/comment-page-1#comment-2204</link>
		<dc:creator>FlossieT</dc:creator>
		<pubDate>Thu, 25 Feb 2010 12:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.takaitra.com/?p=234#comment-2204</guid>
		<description>This is really excellent work - thank you. This is probably not the place to ask for support but - I&#039;m completely new to the WP Trac system! I&#039;m running 2.9.2 - what&#039;s the best way to apply your patch?</description>
		<content:encoded><![CDATA[<p>This is really excellent work &#8211; thank you. This is probably not the place to ask for support but &#8211; I&#8217;m completely new to the WP Trac system! I&#8217;m running 2.9.2 &#8211; what&#8217;s the best way to apply your patch?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Takaitra</title>
		<link>http://www.takaitra.com/posts/234/comment-page-1#comment-2179</link>
		<dc:creator>Takaitra</dc:creator>
		<pubDate>Mon, 18 Jan 2010 02:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.takaitra.com/?p=234#comment-2179</guid>
		<description>&lt;a href=&quot;#comment-2178&quot; rel=&quot;nofollow&quot;&gt;@Sam Burdge&lt;/a&gt; 
Hi Sam,
I forgot to mention it in my post, but the patch I submitted for the  wp_list_authors template tag does indeed streamline the SQL so that only one query is performed instead of one for each author. There is an &lt;a href=&quot;http://core.trac.wordpress.org/ticket/5407&quot; rel=&quot;nofollow&quot;&gt;open enhancement request&lt;/a&gt; in WordPress Trac regarding this subject and from which I got some hints on how to write the correct JOIN statements. As you can see, that request is two years old! We can only hope that the &lt;a href=&quot;http://core.trac.wordpress.org/ticket/10329&quot; rel=&quot;nofollow&quot;&gt;wp_list_authors patch&lt;/a&gt; is included in WordPress 3.0 and then at least one template tag will be streamlined.</description>
		<content:encoded><![CDATA[<p><a href="#comment-2178" rel="nofollow">@Sam Burdge</a><br />
Hi Sam,<br />
I forgot to mention it in my post, but the patch I submitted for the  wp_list_authors template tag does indeed streamline the SQL so that only one query is performed instead of one for each author. There is an <a href="http://core.trac.wordpress.org/ticket/5407" rel="nofollow">open enhancement request</a> in WordPress Trac regarding this subject and from which I got some hints on how to write the correct JOIN statements. As you can see, that request is two years old! We can only hope that the <a href="http://core.trac.wordpress.org/ticket/10329" rel="nofollow">wp_list_authors patch</a> is included in WordPress 3.0 and then at least one template tag will be streamlined.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Burdge</title>
		<link>http://www.takaitra.com/posts/234/comment-page-1#comment-2178</link>
		<dc:creator>Sam Burdge</dc:creator>
		<pubDate>Sun, 17 Jan 2010 17:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.takaitra.com/?p=234#comment-2178</guid>
		<description>Hi Takaitra
Your suggestion to improve this function is a great idea. The fact that it has to make one db query per author at the moment means that this one function alone can double or even triple the number of sql queries per page load.

WordPress used to store the &#039;user_status&#039; in the wp_users table, so this function could be performed on a single db query. Wouldn&#039;t that approach be better? as for a simple call of the function it would eliminate the need to make multiple queries to the user_meta table.

In my opinion a main priority for WordPress should be to streamline a lot of its template tags to be less greedy with the number of sql queries. For busy sites with high traffic the extra queries can cause the mysql memory to max out, even when using a caching plugin.</description>
		<content:encoded><![CDATA[<p>Hi Takaitra<br />
Your suggestion to improve this function is a great idea. The fact that it has to make one db query per author at the moment means that this one function alone can double or even triple the number of sql queries per page load.</p>
<p>WordPress used to store the &#8216;user_status&#8217; in the wp_users table, so this function could be performed on a single db query. Wouldn&#8217;t that approach be better? as for a simple call of the function it would eliminate the need to make multiple queries to the user_meta table.</p>
<p>In my opinion a main priority for WordPress should be to streamline a lot of its template tags to be less greedy with the number of sql queries. For busy sites with high traffic the extra queries can cause the mysql memory to max out, even when using a caching plugin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
