<?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: Minify for WordPress and WP Super Cache</title>
	<atom:link href="http://lyncd.com/2008/11/minify-for-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://lyncd.com/2008/11/minify-for-wordpress/</link>
	<description></description>
	<lastBuildDate>Wed, 25 Jan 2012 14:19:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: sticks</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-3206</link>
		<dc:creator>sticks</dc:creator>
		<pubDate>Fri, 24 Sep 2010 03:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-3206</guid>
		<description>This is just a &lt;a href=&quot;http://lyncd.com/wpscmin/&quot; rel=&quot;nofollow&quot;&gt;plugin&lt;/a&gt; to WP Super Cache that runs Minify on HTML pages -- including any inline style rules and JS. It does include an on/off button that it adds to the Super Cache options page in the WordPress backend, so if there&#039;s a problem you can use that to debug whether it&#039;s Super Cache causing the problem or the minification in particular.

If you&#039;re using it and you suspect your browser is computing style rules or script differently as a result of Minify, I&#039;d suggest using your browser&#039;s debugger. You can inspect the DOM, look at computed styles, and obviously there&#039;s the JS console. i.e. Firebug for Firefox or Safari&#039;s built-in debugger.

If you think you find a real bug, report it to the &lt;a href=&quot;http://code.google.com/p/minify/&quot; rel=&quot;nofollow&quot;&gt;Minify project&lt;/a&gt; ... my plugin is just using the standard Minify lib and running it on page contents.

I won&#039;t get into comparing WP Super Cache to Batcache or W3 Total Cache, sorry.</description>
		<content:encoded><![CDATA[<p>This is just a <a href="http://lyncd.com/wpscmin/" rel="nofollow">plugin</a> to WP Super Cache that runs Minify on HTML pages &#8212; including any inline style rules and JS. It does include an on/off button that it adds to the Super Cache options page in the WordPress backend, so if there&#8217;s a problem you can use that to debug whether it&#8217;s Super Cache causing the problem or the minification in particular.</p>
<p>If you&#8217;re using it and you suspect your browser is computing style rules or script differently as a result of Minify, I&#8217;d suggest using your browser&#8217;s debugger. You can inspect the DOM, look at computed styles, and obviously there&#8217;s the JS console. i.e. Firebug for Firefox or Safari&#8217;s built-in debugger.</p>
<p>If you think you find a real bug, report it to the <a href="http://code.google.com/p/minify/" rel="nofollow">Minify project</a> &#8230; my plugin is just using the standard Minify lib and running it on page contents.</p>
<p>I won&#8217;t get into comparing WP Super Cache to Batcache or W3 Total Cache, sorry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-3205</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Fri, 24 Sep 2010 02:44:38 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-3205</guid>
		<description>I have tried using minify only but the theme seems to break away when I use minify.. Does the plugin have any options to debug why the the CSS / JS breaks? Additionally how does the plugin compare against the W3 total cache?</description>
		<content:encoded><![CDATA[<p>I have tried using minify only but the theme seems to break away when I use minify.. Does the plugin have any options to debug why the the CSS / JS breaks? Additionally how does the plugin compare against the W3 total cache?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sticks</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-2915</link>
		<dc:creator>sticks</dc:creator>
		<pubDate>Wed, 11 Aug 2010 06:31:20 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-2915</guid>
		<description>OK, it&#039;s done! My code is now a plugin to WP Super Cache, so no patches necessary, and it should not break in the future when Super Cache changes.

The new version is on this &lt;a href=&quot;/wpscmin/&quot; title=&quot;WPSCMin, an HTML Minify plugin for WordPress and WP Super Cache&quot; rel=&quot;nofollow&quot;&gt;separate project page&lt;/a&gt;. I&#039;ll add an announcement post soon.</description>
		<content:encoded><![CDATA[<p>OK, it&#8217;s done! My code is now a plugin to WP Super Cache, so no patches necessary, and it should not break in the future when Super Cache changes.</p>
<p>The new version is on this <a href="/wpscmin/" title="WPSCMin, an HTML Minify plugin for WordPress and WP Super Cache" rel="nofollow">separate project page</a>. I&#8217;ll add an announcement post soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sticks</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-2826</link>
		<dc:creator>sticks</dc:creator>
		<pubDate>Mon, 02 Aug 2010 05:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-2826</guid>
		<description>Yes, after a bit of a layoff I&#039;m back in the WordPress game and will ping you when it&#039;s updated. Parts of WP Super Cache where the patch inserts its hooks have been reorganized, so once I&#039;m done tracing the new code and testing, I&#039;ll have a new version.</description>
		<content:encoded><![CDATA[<p>Yes, after a bit of a layoff I&#8217;m back in the WordPress game and will ping you when it&#8217;s updated. Parts of WP Super Cache where the patch inserts its hooks have been reorganized, so once I&#8217;m done tracing the new code and testing, I&#8217;ll have a new version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Des Geeks et des lettres</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-1376</link>
		<dc:creator>Des Geeks et des lettres</dc:creator>
		<pubDate>Sun, 13 Dec 2009 17:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-1376</guid>
		<description>Thanx for this great plugin, but if i upgrade Super-cache minify doesn&#039;t work anymore ; not bad i stay with the 0.91 version but in the future will you patch your great plugin ? Thx.</description>
		<content:encoded><![CDATA[<p>Thanx for this great plugin, but if i upgrade Super-cache minify doesn&#8217;t work anymore ; not bad i stay with the 0.91 version but in the future will you patch your great plugin ? Thx.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sticks</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-180</link>
		<dc:creator>sticks</dc:creator>
		<pubDate>Mon, 16 Mar 2009 10:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-180</guid>
		<description>FYI, new release 0.3 to patch with WP Super Cache 0.9.1. Scroll back up to the updated &lt;a href=&quot;#install&quot; rel=&quot;nofollow&quot;&gt;install&lt;/a&gt; and &lt;a href=&quot;#versions&quot; rel=&quot;nofollow&quot;&gt;versions&lt;/a&gt; sections! This release also makes the change suggested by MrClay for compatibility with pre-5.2.3 versions of PHP.

No other/real changes made, so unless you want to update to Super Cache 0.9.1 or are running pre-5.2.3 PHP, the old &quot;version&quot; is the same as this one.</description>
		<content:encoded><![CDATA[<p>FYI, new release 0.3 to patch with WP Super Cache 0.9.1. Scroll back up to the updated <a href="#install" rel="nofollow">install</a> and <a href="#versions" rel="nofollow">versions</a> sections! This release also makes the change suggested by MrClay for compatibility with pre-5.2.3 versions of PHP.</p>
<p>No other/real changes made, so unless you want to update to Super Cache 0.9.1 or are running pre-5.2.3 PHP, the old &#8220;version&#8221; is the same as this one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sticks</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-179</link>
		<dc:creator>sticks</dc:creator>
		<pubDate>Mon, 16 Mar 2009 07:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-179</guid>
		<description>Nice timing, I think &lt;a href=&quot;http://lyncd.com/2009/02/update-minify-wordpress-wp-super-cache/#comment-174&quot; rel=&quot;nofollow&quot;&gt;this is him&lt;/a&gt; on the update post.

It looks like you&#039;ve got it figured out already, thank you! I&#039;m happy to change this to the old syntax to save everyone headaches.

As a sysadmin I would be remiss not to mention that it is generally a seriously bad idea security-wise to be running outdated versions of PHP, as there are pretty regular security problems/exploits discovered, including some nasty ones since 5.2.3. Of course, I realize this is totally beyond many people&#039;s control, but it is what they should demand of their hosting providers, too. There are some things (2.4 kernel!) where running old and stable on your servers is good, but running old releases of PHP5 is very bad!

/end offtopic editorial</description>
		<content:encoded><![CDATA[<p>Nice timing, I think <a href="http://lyncd.com/2009/02/update-minify-wordpress-wp-super-cache/#comment-174" rel="nofollow">this is him</a> on the update post.</p>
<p>It looks like you&#8217;ve got it figured out already, thank you! I&#8217;m happy to change this to the old syntax to save everyone headaches.</p>
<p>As a sysadmin I would be remiss not to mention that it is generally a seriously bad idea security-wise to be running outdated versions of PHP, as there are pretty regular security problems/exploits discovered, including some nasty ones since 5.2.3. Of course, I realize this is totally beyond many people&#8217;s control, but it is what they should demand of their hosting providers, too. There are some things (2.4 kernel!) where running old and stable on your servers is good, but running old releases of PHP5 is very bad!</p>
<p>/end offtopic editorial</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mrclay</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-176</link>
		<dc:creator>mrclay</dc:creator>
		<pubDate>Sun, 15 Mar 2009 17:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-176</guid>
		<description>One user is experiencing an &lt;a href=&quot;http://groups.google.com/group/minify/browse_thread/thread/3781cbaf19a9f770&quot; rel=&quot;nofollow&quot;&gt;issue&lt;/a&gt; where JSMin seems to be returning &lt;code&gt;&quot; &quot;&lt;/code&gt; rather than the adsense code.

This might be due to your &lt;code&gt;&quot;JSMin::minify&quot;&lt;/code&gt; callback syntax, which only became valid in PHP 5.2.3. Using &lt;code&gt;array(&quot;JSMin&quot;, &quot;minify&quot;)&lt;/code&gt; wouldn&#039;t cost anything and would gain compatibility.</description>
		<content:encoded><![CDATA[<p>One user is experiencing an <a href="http://groups.google.com/group/minify/browse_thread/thread/3781cbaf19a9f770" rel="nofollow">issue</a> where JSMin seems to be returning <code>" "</code> rather than the adsense code.</p>
<p>This might be due to your <code>"JSMin::minify"</code> callback syntax, which only became valid in PHP 5.2.3. Using <code>array("JSMin", "minify")</code> wouldn&#8217;t cost anything and would gain compatibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sticks</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-122</link>
		<dc:creator>sticks</dc:creator>
		<pubDate>Mon, 23 Feb 2009 13:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-122</guid>
		<description>FYI all, I&#039;ve updated the mod to work with the current version of WP Super Cache, 0.9, and updated the &lt;a href=&quot;#install&quot; rel=&quot;nofollow&quot;&gt;install instructions&lt;/a&gt; and download links accordingly. The original files for use with Super Cache 0.8.x are still there, too.

I wrote up a &lt;a href=&quot;/2009/02/update-minify-wordpress-wp-super-cache/&quot; rel=&quot;nofollow&quot;&gt;quick post with more info&lt;/a&gt; so there&#039;d be some kind of notification in the feed -- check it out for a little more info on what&#039;s changed.</description>
		<content:encoded><![CDATA[<p>FYI all, I&#8217;ve updated the mod to work with the current version of WP Super Cache, 0.9, and updated the <a href="#install" rel="nofollow">install instructions</a> and download links accordingly. The original files for use with Super Cache 0.8.x are still there, too.</p>
<p>I wrote up a <a href="/2009/02/update-minify-wordpress-wp-super-cache/" rel="nofollow">quick post with more info</a> so there&#8217;d be some kind of notification in the feed &#8212; check it out for a little more info on what&#8217;s changed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sticks</title>
		<link>http://lyncd.com/2008/11/minify-for-wordpress/comment-page-1/#comment-93</link>
		<dc:creator>sticks</dc:creator>
		<pubDate>Sat, 14 Feb 2009 02:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://lyncd.com/?p=33#comment-93</guid>
		<description>Yeah, agreed re: nuisance. See my comments to Ghosttie -- almost everything I&#039;ve done is in a standalone class, but I couldn&#039;t find any other way to hook this into WP Super Cache without hacking the code.

Fortunately, the patch is just a couple of lines (I tried to keep hacks to bare minimum), so it&#039;s pretty simple to just go in and make the edits manually, if applying it automatically fails. I totally agree that this isn&#039;t ideal -- if you can figure out a better way to do it, please let me know! Thanks for the interest.</description>
		<content:encoded><![CDATA[<p>Yeah, agreed re: nuisance. See my comments to Ghosttie &#8212; almost everything I&#8217;ve done is in a standalone class, but I couldn&#8217;t find any other way to hook this into WP Super Cache without hacking the code.</p>
<p>Fortunately, the patch is just a couple of lines (I tried to keep hacks to bare minimum), so it&#8217;s pretty simple to just go in and make the edits manually, if applying it automatically fails. I totally agree that this isn&#8217;t ideal &#8212; if you can figure out a better way to do it, please let me know! Thanks for the interest.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

