<blockquote style="margin: 0pt 0pt 0pt 6.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; color: rgb(153, 153, 153);" class="gmail_quote"><i>I would argue that this is the desired result. Themes shouldn't be <br>
attempting to modify what plugins do. <br></i></blockquote><br>I agree--ideally, themes and plugins would function as separate <br>"abstraction layers"--but theme developers can't assume the ideal case; <br>
they must assume the worst case. The reality we must face is that <br>WordPress plugins and themes share the same APIs, and most developers <br>write code without giving adequate consideration to its effects on the <br>global level. Simply put, it doesn't make sense to create theme <br>
requirements based on the assumption that all plugins are coded "the <br>right way," when the fact is...many (most?) are not. <br><br><br><br><blockquote style="margin: 0pt 0pt 0pt 6.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; color: rgb(153, 153, 153);" class="gmail_quote">
<i>The user can do that anyway, and in a much more sane way. If the plugin <br>is hooked into wp_head, then it's using an action hook to do it. <br>Modifying the output is simply a matter of removing the plugin's hook <br>
using remove_action and then adding its own hook using add_action. <br></i></blockquote><br>I already addressed this. <br><br><br><br><blockquote style="margin: 0pt 0pt 0pt 6.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; color: rgb(153, 153, 153);" class="gmail_quote">
<i>Plugins should not include jQuery, as it's built into WordPress. <br>Multiple plugins can wp_enqueue_script('jquery') all day long and only <br>one jquery script gets put into the header. <br><br>Correcting the plugin that is doing this incorrectly is the better <br>
alternative. <br></i></blockquote><br>I already addressed this. <br><br><br><br><blockquote style="margin: 0pt 0pt 0pt 6.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; color: rgb(153, 153, 153);" class="gmail_quote">
<i>remove_action alone, without an alternate function add, would work for <br>most of these cases. <br></i></blockquote><br>Most, but not all. What is your argument here...that we should prevent <br>themes from giving admins the ability to achieve GREAT because WordPress <br>
core already provides GOOD? <br><br><br><br><blockquote style="margin: 0pt 0pt 0pt 6.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; color: rgb(153, 153, 153);" class="gmail_quote"><i>CSS and JS should be using the proper enqueue script/style methods, <br>
avoiding this anyway. Fixing the plugin is preferable. <br></i></blockquote><br>Again, wishful thinking isn't a valid reason for rejecting themes that <br>cater to real-world problems. <br><br><br><br><blockquote style="margin: 0pt 0pt 0pt 6.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex; color: rgb(153, 153, 153);" class="gmail_quote">
<i>If a plugin is using an older version of jquery or is maintaining <br>back-compat all the way to 2.8, then please notify the author of the <br>plugin that he's doing it wrong. I'd even be inclined to remove such <br>
plugins from the directory, as they're badly out of date. <br></i></blockquote><br>According to the <a href="http://wordpress.org/about/stats/">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?