Somehow, we seem to be on completely different pages, and I am unsure why.<div><br></div><div>Let's start with Plugins adding content to the HTML document head. As far as I understand, a Plugin has two primary options for injecting such content:</div>
<div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>1) Using <b>wp_enqueue_style()</b> or <b>wp_enqueue_script()</b></div><div><br></div><div>2) Using <b>add_action( 'wp_head', 'some_custom_function' )</b>, where <b>some_custom_function()</b> prints a fully formed script or style tag, or whatever other content.</div>
</blockquote><div><br></div><div>If these are the only two options, then I stand by my assertion that adding an ob_cache layer on top of the core Hooks API is unnecessary, because <i>both of these options already have means within core functionality to be undone</i>:</div>
<div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>1) Anything hooked in using <b>wp_enqueue_style()</b> or <b>wp_enqueue_script()</b> can be undone by calling <b><font class="Apple-style-span" color="#ff0000">wp_dequeue_style()</font></b> and <b><font class="Apple-style-span" color="#ff0000">wp_dequeue_script()</font></b>, respectively.</div>
<div><br></div><div>2) Anything hooked in using <b>add_action( 'wp_head', 'some_custom_function' )</b> can be undone by calling <b><font class="Apple-style-span" color="#ff0000">remove_action( 'wp_head', 'some_custom_function' )</font></b></div>
</blockquote><div><br></div><div>Am I missing any options? Are there any other ways for Plugins to inject content into the HTML document head? </div><div><br><div class="gmail_quote">On Sat, Jul 2, 2011 at 7:30 PM, Darren Slatten <span dir="ltr"><<a href="mailto:darrenslatten@gmail.com">darrenslatten@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br></div>According to the <a href="http://wordpress.org/about/stats/" target="_blank">WP stats</a>, the number of sites using WordPress versions <br>2.7 and older represents 9.4% of all WordPress users. You're saying that <br>
any plugin that attempts to maintain backwards compatibility with those <br>(millions of) sites by hooking a jQuery reference directly to wp_head <br>(instead of using wp_enqueue_script) should be banned from the plugin <br>
directory?</blockquote><div><br></div><div>Again here speaking based solely my opinion only: I agree with Otto. Themes and Plugins hosted by WordPress.org absolutely should not be promoting, encouraging, or facilitating users to be using outdated, insecure versions of WordPress. </div>
<div><br></div><div>Just FYI: the decision point regarding dropping WordPress official support for PHP4 was <b>10%</b>. It appears the IE6 support has been handled in much the same way. So, officially not supporting the 9.4% of WordPress users who are using 2.7 and older versions of WordPress is, IMHO, entirely reasonable.</div>
<div><br></div><div>How such repository-hosted Plugins get handled, I leave to others. But I would agree with a decision to suspend them.</div><div><br></div><div>Chip</div></div></div>