<?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: Managing Comments With Ajax Edit Comments</title>
	<atom:link href="http://www.wptavern.com/managing-comments-with-ajax-edit-comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments</link>
	<description>Where Every Drink Is On The House</description>
	<lastBuildDate>Mon, 06 Sep 2010 16:48:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jean-Paul Horn</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4754</link>
		<dc:creator>Jean-Paul Horn</dc:creator>
		<pubDate>Fri, 13 Nov 2009 13:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4754</guid>
		<description>@&lt;a href=&quot;#comment-4747&quot; rel=&quot;nofollow&quot;&gt;Jean-Paul Horn&lt;/a&gt; - Hate to correct myself, but although I deinstalled Comment Contest the double queries still show with AEC enabeld. Would appreciate a thorough look if this has been fixed or has crept up again in recent versions.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4747" rel="nofollow">Jean-Paul Horn</a> &#8211; Hate to correct myself, but although I deinstalled Comment Contest the double queries still show with AEC enabeld. Would appreciate a thorough look if this has been fixed or has crept up again in recent versions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Paul Horn</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4747</link>
		<dc:creator>Jean-Paul Horn</dc:creator>
		<pubDate>Thu, 12 Nov 2009 15:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4747</guid>
		<description>@&lt;a href=&quot;#comment-4729&quot; rel=&quot;nofollow&quot;&gt;Ronald&lt;/a&gt; - Heads up for Ronald. The high query count wasn&#039;t due to AEC, but to another plugin I recently installed (Comment Contest). My apologies for the error, although I still wonder why the query count went down after deactivating AEC. And I&#039;d still like to reiterate my request for completely disabling AEC on closed comments ;)</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4729" rel="nofollow">Ronald</a> &#8211; Heads up for Ronald. The high query count wasn&#8217;t due to AEC, but to another plugin I recently installed (Comment Contest). My apologies for the error, although I still wonder why the query count went down after deactivating AEC. And I&#8217;d still like to reiterate my request for completely disabling AEC on closed comments ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Paul Horn</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4730</link>
		<dc:creator>Jean-Paul Horn</dc:creator>
		<pubDate>Tue, 10 Nov 2009 23:21:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4730</guid>
		<description>@&lt;a href=&quot;#comment-4729&quot; rel=&quot;nofollow&quot;&gt;Ronald&lt;/a&gt; - Thanks again, Ronald. Appreciate the quick replies! If possible, I&#039;d still like to have an option to either completely disable AEC on posts with closed comments or at least prevent AEC from loading the JS and CSS on posts with closed comments (sort of like the check for is_page() ).</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4729" rel="nofollow">Ronald</a> &#8211; Thanks again, Ronald. Appreciate the quick replies! If possible, I&#8217;d still like to have an option to either completely disable AEC on posts with closed comments or at least prevent AEC from loading the JS and CSS on posts with closed comments (sort of like the check for is_page() ).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4729</link>
		<dc:creator>Ronald</dc:creator>
		<pubDate>Tue, 10 Nov 2009 23:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4729</guid>
		<description>@&lt;a href=&quot;#comment-4728&quot; rel=&quot;nofollow&quot;&gt;Jean-Paul Horn&lt;/a&gt; -
that&#039;s odd. I thought we addressed the query problem in a previous version. I&#039;ll take a look.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4728" rel="nofollow">Jean-Paul Horn</a> -<br />
that&#8217;s odd. I thought we addressed the query problem in a previous version. I&#8217;ll take a look.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Paul Horn</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4728</link>
		<dc:creator>Jean-Paul Horn</dc:creator>
		<pubDate>Tue, 10 Nov 2009 22:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4728</guid>
		<description>@&lt;a href=&quot;#comment-4700&quot; rel=&quot;nofollow&quot;&gt;Ronald&lt;/a&gt; - Good to hear, thanks!
I do have another question. Am I correct AEC adds two queries per comment? Weird thing is, on one of our really popular posts (contest post) we have over 800 queries. With AEC enabled this translates into 
&lt;code&gt;1704 queries. 6.600 seconds.&lt;/code&gt;
If I deactivate AEC, I only have 46 queries on the same post ... Ofcourse, this really hurts performance, especially on posts where we have over 50 comments (happens more often than not).

Problem is - like I said before - we can&#039;t uninstall this plugin as our users would come lynching me ;) Is there a way to completely prevent AEC from executing at all when comments are closed? (we automatically close all posts after three months). This would already help tremendously.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4700" rel="nofollow">Ronald</a> &#8211; Good to hear, thanks!<br />
I do have another question. Am I correct AEC adds two queries per comment? Weird thing is, on one of our really popular posts (contest post) we have over 800 queries. With AEC enabled this translates into<br />
<code>1704 queries. 6.600 seconds.</code><br />
If I deactivate AEC, I only have 46 queries on the same post &#8230; Ofcourse, this really hurts performance, especially on posts where we have over 50 comments (happens more often than not).</p>
<p>Problem is &#8211; like I said before &#8211; we can&#8217;t uninstall this plugin as our users would come lynching me ;) Is there a way to completely prevent AEC from executing at all when comments are closed? (we automatically close all posts after three months). This would already help tremendously.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4718</link>
		<dc:creator>Benjamin</dc:creator>
		<pubDate>Tue, 10 Nov 2009 02:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4718</guid>
		<description>Thanks for this review.  I enjoy reading indepth reviews of plugins (and other wp related info).</description>
		<content:encoded><![CDATA[<p>Thanks for this review.  I enjoy reading indepth reviews of plugins (and other wp related info).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4710</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 09 Nov 2009 16:40:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4710</guid>
		<description>Ah good, the new version is now working fine (it wasn&#039;t the case with thickbox, probably due to a plugin conflict).

I would very much like to see Jean-Paul&#039;s ideas implemented !</description>
		<content:encoded><![CDATA[<p>Ah good, the new version is now working fine (it wasn&#8217;t the case with thickbox, probably due to a plugin conflict).</p>
<p>I would very much like to see Jean-Paul&#8217;s ideas implemented !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Indrek</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4703</link>
		<dc:creator>Indrek</dc:creator>
		<pubDate>Mon, 09 Nov 2009 09:49:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4703</guid>
		<description>Thank you for this great review. Until now I hadn&#039;t really looked into it but after seeing it&#039;s great features I think I&#039;ll definitely add it to my blog. Thanks again!</description>
		<content:encoded><![CDATA[<p>Thank you for this great review. Until now I hadn&#8217;t really looked into it but after seeing it&#8217;s great features I think I&#8217;ll definitely add it to my blog. Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4700</link>
		<dc:creator>Ronald</dc:creator>
		<pubDate>Mon, 09 Nov 2009 01:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4700</guid>
		<description>@&lt;a href=&quot;#comment-4697&quot; rel=&quot;nofollow&quot;&gt;Jean-Paul Horn&lt;/a&gt; -
thanks for the feedback. I&#039;ll see what we can do to improve performance based on your suggestions.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-4697" rel="nofollow">Jean-Paul Horn</a> -<br />
thanks for the feedback. I&#8217;ll see what we can do to improve performance based on your suggestions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Paul Horn</title>
		<link>http://www.wptavern.com/managing-comments-with-ajax-edit-comments#comment-4697</link>
		<dc:creator>Jean-Paul Horn</dc:creator>
		<pubDate>Sun, 08 Nov 2009 23:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=2806#comment-4697</guid>
		<description>I just *LOVE* this plugin and so do our users. I love the new ColorBox addition (much faster!) and generally come to appreciate all the new features which have been put in older and recent versions.

I do have some wishes, focussed on performance enhancements (I&#039;m trying to cut down on as much overhead http requests as possible, but AEC has proven rather difficult to trim.

1. I believe &lt;em&gt;function add_script_vars&lt;/em&gt; (line 46) can be easily changed to wp_footer instead of wp_head (I need to do this after every upgrade). Also, most Javascript files (&lt;em&gt;function add_scripts, lines 1452-14890&lt;/em&gt;) could also benefit from switching to loading in the footer (I believe this is only for newer WP versions through wp_enqueue_script, but would love to see a conditional for this) (again, works fine in my installation, but need to do this after every new version of AEC)

(my code change for line 46)
&lt;code&gt;
		add_action(&#039;wp_footer&#039;, array(&amp;$this, &#039;add_script_vars&#039;), 1001);
&lt;/code&gt;
(my code changes for lines 1460-1461)
&lt;code&gt;
			wp_enqueue_script(&#039;colorbox&#039;, $this-&gt;pluginDir . &#039;/js/jquery.colorbox-min.js&#039;, array(&quot;jquery&quot;), &#039;&#039;, true);
			wp_enqueue_script(&#039;wp_ajax_edit_comments_script&#039;, $this-&gt;pluginDir . &#039;/js/wp-ajax-edit-comments.js&#039;, array(&quot;jquery&quot;, &quot;wp-ajax-response&quot;, &quot;colorbox&quot;) , 2.3, true);
&lt;/code&gt;

2. An &lt;strong&gt;even better option&lt;/strong&gt; would be to let advanced users disable loading of all the JS files and variables, so we could offload these to a CDN (like you let us define our own CSS files, albeit this won&#039;t let us offload to another server, since it has to be a relative path). This also goes for additional css files like the new colorbox.css.

3. If option &#039;No icons&#039; is chosen (&lt;em&gt;Styles &gt; Determine Icon Display/Sets&lt;/em&gt;), AEC still loads the selected icons css file (e.g. wp-ajax-edit-comments/css/themes/circular/edit-comments.css) and thus all the (redudant) icon images in that css file. Maybe a separate &#039;no-icons&#039; theme would be a solution?


Other than this, one of the best WordPress plugins out there, both for admins *and* users. Thanks for all your hard work (and thanks to Ajay too!)

P.S. Most of my wishes only affect the user side of AEC. I don&#039;t really mind about what extra stuff is loaded for admins (either front or dashboard)</description>
		<content:encoded><![CDATA[<p>I just *LOVE* this plugin and so do our users. I love the new ColorBox addition (much faster!) and generally come to appreciate all the new features which have been put in older and recent versions.</p>
<p>I do have some wishes, focussed on performance enhancements (I&#8217;m trying to cut down on as much overhead http requests as possible, but AEC has proven rather difficult to trim.</p>
<p>1. I believe <em>function add_script_vars</em> (line 46) can be easily changed to wp_footer instead of wp_head (I need to do this after every upgrade). Also, most Javascript files (<em>function add_scripts, lines 1452-14890</em>) could also benefit from switching to loading in the footer (I believe this is only for newer WP versions through wp_enqueue_script, but would love to see a conditional for this) (again, works fine in my installation, but need to do this after every new version of AEC)</p>
<p>(my code change for line 46)<br />
<code><br />
		add_action('wp_footer', array(&amp;$this, 'add_script_vars'), 1001);<br />
</code><br />
(my code changes for lines 1460-1461)<br />
<code><br />
			wp_enqueue_script('colorbox', $this-&gt;pluginDir . '/js/jquery.colorbox-min.js', array("jquery"), '', true);<br />
			wp_enqueue_script('wp_ajax_edit_comments_script', $this-&gt;pluginDir . '/js/wp-ajax-edit-comments.js', array("jquery", "wp-ajax-response", "colorbox") , 2.3, true);<br />
</code></p>
<p>2. An <strong>even better option</strong> would be to let advanced users disable loading of all the JS files and variables, so we could offload these to a CDN (like you let us define our own CSS files, albeit this won&#8217;t let us offload to another server, since it has to be a relative path). This also goes for additional css files like the new colorbox.css.</p>
<p>3. If option &#8216;No icons&#8217; is chosen (<em>Styles &gt; Determine Icon Display/Sets</em>), AEC still loads the selected icons css file (e.g. wp-ajax-edit-comments/css/themes/circular/edit-comments.css) and thus all the (redudant) icon images in that css file. Maybe a separate &#8216;no-icons&#8217; theme would be a solution?</p>
<p>Other than this, one of the best WordPress plugins out there, both for admins *and* users. Thanks for all your hard work (and thanks to Ajay too!)</p>
<p>P.S. Most of my wishes only affect the user side of AEC. I don&#8217;t really mind about what extra stuff is loaded for admins (either front or dashboard)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/


Served from: www.wptavern.com @ 2010-09-09 12:48:16 -->