Thanks for the &quot;heads up&quot;, Nacin;<br><br>We&#39;ll look into referencing this on the Theme Review page(s), too.<br><br><br>Cais.<br><br><div class="gmail_quote">On Sun, Sep 19, 2010 at 8:16 PM, Andrew Nacin <span dir="ltr">&lt;<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">A heads up, I&#39;ve removed references to read-only parameters for add_theme_support() from <a href="http://codex.wordpress.org/Function_Reference/add_theme_support" target="_blank">http://codex.wordpress.org/Function_Reference/add_theme_support</a>.<div>



<br></div><div>Any theme enabling &#39;editor-style&#39;, &#39;menus&#39;, &#39;custom-header&#39;, &#39;custom-background&#39;, or &#39;widgets&#39; via add_theme_support() is doing it wrong. These are internal registrations so we can transparently use current_theme_support(). In fact WordPress prevents these in particular from being removed via remove_theme_support(), that way there are no imbalances.</div>



<div><br></div><font color="#888888"><div>Nacin</div>
</font><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br>