<?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 for Colin Mollenhour's Technical Blog</title>
	<atom:link href="http://colin.mollenhour.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://colin.mollenhour.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sun, 31 Jan 2010 04:20:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Module Manager Update, now on Google Code! by Colin Mollenhour&#8217;s Technical Blog &#187; Module Manager &#8211; for when svn:externals just doesn&#8217;t cut it.</title>
		<link>http://colin.mollenhour.com/2010/01/31/module-manager-update/comment-page-1/#comment-57</link>
		<dc:creator>Colin Mollenhour&#8217;s Technical Blog &#187; Module Manager &#8211; for when svn:externals just doesn&#8217;t cut it.</dc:creator>
		<pubDate>Sun, 31 Jan 2010 04:20:01 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=109#comment-57</guid>
		<description>[...] Update 1/30/2010: Added nested modules, renamed .modman file to modman, released under Apache License 2.0, and hosted on Google Code. [...]</description>
		<content:encoded><![CDATA[<p>[...] Update 1/30/2010: Added nested modules, renamed .modman file to modman, released under Apache License 2.0, and hosted on Google Code. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Module Manager &#8211; for when svn:externals just doesn&#8217;t cut it. by Colin Mollenhour&#8217;s Technical Blog &#187; Module Manager Update, now on Google Code!</title>
		<link>http://colin.mollenhour.com/2009/10/17/module-manager-for-when-svnexternals-just-doesnt-cut-it/comment-page-1/#comment-56</link>
		<dc:creator>Colin Mollenhour&#8217;s Technical Blog &#187; Module Manager Update, now on Google Code!</dc:creator>
		<pubDate>Sun, 31 Jan 2010 04:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=96#comment-56</guid>
		<description>[...] recently updated Module Manager (first post) to support nested modules and renamed the .modman definitions file to simply modman for easier [...]</description>
		<content:encoded><![CDATA[<p>[...] recently updated Module Manager (first post) to support nested modules and renamed the .modman definitions file to simply modman for easier [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Yet Another &#8220;Hiding Out-Of-Stock Products&#8221; Update by colin</title>
		<link>http://colin.mollenhour.com/2009/09/28/yet-another-hiding-out-of-stock-products-update/comment-page-1/#comment-52</link>
		<dc:creator>colin</dc:creator>
		<pubDate>Thu, 14 Jan 2010 15:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=84#comment-52</guid>
		<description>I would instead observe an event. Off the top of my head I think cataloginventory_stock_status_save_after would be a good starting point. If the status is changed to out of stock then disable the related product. I haven&#039;t fully thought this through or tested but I think it could work. Note, then, that you would no longer need the Lucky_InStockOnly module.</description>
		<content:encoded><![CDATA[<p>I would instead observe an event. Off the top of my head I think cataloginventory_stock_status_save_after would be a good starting point. If the status is changed to out of stock then disable the related product. I haven&#8217;t fully thought this through or tested but I think it could work. Note, then, that you would no longer need the Lucky_InStockOnly module.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Yet Another &#8220;Hiding Out-Of-Stock Products&#8221; Update by point4design</title>
		<link>http://colin.mollenhour.com/2009/09/28/yet-another-hiding-out-of-stock-products-update/comment-page-1/#comment-51</link>
		<dc:creator>point4design</dc:creator>
		<pubDate>Thu, 14 Jan 2010 12:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=84#comment-51</guid>
		<description>For example, is there a script I could run (by cron) to set products to disabled if the stock equals zero?</description>
		<content:encoded><![CDATA[<p>For example, is there a script I could run (by cron) to set products to disabled if the stock equals zero?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Yet Another &#8220;Hiding Out-Of-Stock Products&#8221; Update by point4design</title>
		<link>http://colin.mollenhour.com/2009/09/28/yet-another-hiding-out-of-stock-products-update/comment-page-1/#comment-50</link>
		<dc:creator>point4design</dc:creator>
		<pubDate>Wed, 13 Jan 2010 21:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=84#comment-50</guid>
		<description>Thanks for the quick response. Do you know a way then to easily &#039;disable&#039; products that are out of stock?</description>
		<content:encoded><![CDATA[<p>Thanks for the quick response. Do you know a way then to easily &#8216;disable&#8217; products that are out of stock?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Yet Another &#8220;Hiding Out-Of-Stock Products&#8221; Update by colin</title>
		<link>http://colin.mollenhour.com/2009/09/28/yet-another-hiding-out-of-stock-products-update/comment-page-1/#comment-49</link>
		<dc:creator>colin</dc:creator>
		<pubDate>Wed, 13 Jan 2010 18:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=84#comment-49</guid>
		<description>This is the &quot;Known Bug&quot; which is really a limitation of Magento&#039;s query design. I fixed this for a client (triercopenhagen.com) a few months ago but it took *forever* and the solution is not something that is readily distributable and it isn&#039;t tested with grouped products and simple products and various other Magento features. The way the layered nav query is constructed is completely backwards from the original and it is quite complex so I don&#039;t know if I can fully recommend going down that path.. I think Varien made a huge design mistake when they decided to not have the ability to hide out of stock products built into the core.</description>
		<content:encoded><![CDATA[<p>This is the &#8220;Known Bug&#8221; which is really a limitation of Magento&#8217;s query design. I fixed this for a client (triercopenhagen.com) a few months ago but it took *forever* and the solution is not something that is readily distributable and it isn&#8217;t tested with grouped products and simple products and various other Magento features. The way the layered nav query is constructed is completely backwards from the original and it is quite complex so I don&#8217;t know if I can fully recommend going down that path.. I think Varien made a huge design mistake when they decided to not have the ability to hide out of stock products built into the core.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Yet Another &#8220;Hiding Out-Of-Stock Products&#8221; Update by point4design</title>
		<link>http://colin.mollenhour.com/2009/09/28/yet-another-hiding-out-of-stock-products-update/comment-page-1/#comment-48</link>
		<dc:creator>point4design</dc:creator>
		<pubDate>Wed, 13 Jan 2010 17:13:44 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=84#comment-48</guid>
		<description>I&#039;m having a problem with the extension. I have a &#039;size&#039; attribute that I use on many of my configurable products. I have some of these configurable items in a clearance section and this is the only category I use layered navigation on (just activated it). I&#039;ve noticed that in the layered navigation for the size attribute it is showing products that don&#039;t have any stock. Category is here: http://www.wildernessrunning.com/shop/index.php/screaming-deals. If you click the &#039;extra large&#039; in the layered nav on the right, the first product listed shouldn&#039;t be there as it doesn&#039;t have any extra large in stock. Can you help me figure this out?</description>
		<content:encoded><![CDATA[<p>I&#8217;m having a problem with the extension. I have a &#8217;size&#8217; attribute that I use on many of my configurable products. I have some of these configurable items in a clearance section and this is the only category I use layered navigation on (just activated it). I&#8217;ve noticed that in the layered navigation for the size attribute it is showing products that don&#8217;t have any stock. Category is here: <a href="http://www.wildernessrunning.com/shop/index.php/screaming-deals" rel="nofollow">http://www.wildernessrunning.com/shop/index.php/screaming-deals</a>. If you click the &#8216;extra large&#8217; in the layered nav on the right, the first product listed shouldn&#8217;t be there as it doesn&#8217;t have any extra large in stock. Can you help me figure this out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Module Manager &#8211; for when svn:externals just doesn&#8217;t cut it. by colin</title>
		<link>http://colin.mollenhour.com/2009/10/17/module-manager-for-when-svnexternals-just-doesnt-cut-it/comment-page-1/#comment-47</link>
		<dc:creator>colin</dc:creator>
		<pubDate>Thu, 07 Jan 2010 23:00:47 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=96#comment-47</guid>
		<description>That is great, but the purpose of externals in this case is to separate your code from core code. With svn:externals you would have to mirror the Magento directory structure in your repository which would mean using more than one repository in your installation would most likely not work (can&#039;t have two subdirectories checked out in one subdirectory), and you would either have to use svn:ignore *extremely heavily* or your svn status output would be ridiculous (not to mention, slow). The use of softlinks allows you to version only the code that is yours, organize it cleanly, edit it without wading through thousands of core files, and keep svn commands quick. Since intermediate directories are created automatically but not versioned (unlike with svn:externals with files) there is no problem when using multiple modules from different repositories.</description>
		<content:encoded><![CDATA[<p>That is great, but the purpose of externals in this case is to separate your code from core code. With svn:externals you would have to mirror the Magento directory structure in your repository which would mean using more than one repository in your installation would most likely not work (can&#8217;t have two subdirectories checked out in one subdirectory), and you would either have to use svn:ignore *extremely heavily* or your svn status output would be ridiculous (not to mention, slow). The use of softlinks allows you to version only the code that is yours, organize it cleanly, edit it without wading through thousands of core files, and keep svn commands quick. Since intermediate directories are created automatically but not versioned (unlike with svn:externals with files) there is no problem when using multiple modules from different repositories.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Module Manager &#8211; for when svn:externals just doesn&#8217;t cut it. by melicerte</title>
		<link>http://colin.mollenhour.com/2009/10/17/module-manager-for-when-svnexternals-just-doesnt-cut-it/comment-page-1/#comment-46</link>
		<dc:creator>melicerte</dc:creator>
		<pubDate>Wed, 06 Jan 2010 13:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=96#comment-46</guid>
		<description>Subversion  1.6 support svn:externals on a single file.</description>
		<content:encoded><![CDATA[<p>Subversion  1.6 support svn:externals on a single file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Yet Another &#8220;Hiding Out-Of-Stock Products&#8221; Update by colin</title>
		<link>http://colin.mollenhour.com/2009/09/28/yet-another-hiding-out-of-stock-products-update/comment-page-1/#comment-45</link>
		<dc:creator>colin</dc:creator>
		<pubDate>Sat, 07 Nov 2009 17:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://colin.mollenhour.com/?p=84#comment-45</guid>
		<description>saho, the filter can be applied like so:
&lt;pre&gt;&lt;code&gt;Mage::getSingleton(&#039;cataloginventory/instockonly&#039;)-&gt;addInStockFilterToCollection($products);&lt;/code&gt;&lt;/pre&gt;
Although the above is not necessary if you are already applying the typical &quot;visibility&quot; filter since the extension overrides those methods. Example:
&lt;pre&gt;&lt;code&gt;Mage::getSingleton(&#039;catalog/product_visibility&#039;)-&gt;addVisibleInCatalogFilterToCollection($products);&lt;/code&gt;&lt;/pre&gt;
That is the proper replacement for the &lt;code&gt;addAttributeToFilter(&#039;visibility&#039;, 4)&lt;/code&gt; in your code.</description>
		<content:encoded><![CDATA[<p>saho, the filter can be applied like so:</p>
<pre><code>Mage::getSingleton('cataloginventory/instockonly')->addInStockFilterToCollection($products);</code></pre>
<p>Although the above is not necessary if you are already applying the typical &#8220;visibility&#8221; filter since the extension overrides those methods. Example:</p>
<pre><code>Mage::getSingleton('catalog/product_visibility')->addVisibleInCatalogFilterToCollection($products);</code></pre>
<p>That is the proper replacement for the <code>addAttributeToFilter('visibility', 4)</code> in your code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
