On Wed, Sep 5, 2012 at 10:43 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":18h">Given that Themes should not be adding post-content shortcodes, removing the wpautop filter from shortcodes should be a non-issue.</div></blockquote><div> </div>Some theme authors provide their own shortcodes for end-users to use that are relevant to the theme and its uniqueness. I do not see a reason why this should change<br>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":18h"><div></div><div>I concur with making this (and any other filter that Themes shouldn't be removing) a *warning* level error.</div>
</div></blockquote><div><br>As noted by @_mfields, there are reasonable use-cases where these filters are removed (and re-added) as well. I would lean much more to the INFO or RECOMMENDED notice levels versus the show-stopper WARNING level, but then again we can always add appropriately written themes to the exempt list as needed.<br>
<br><br>Cais.<br><br>PS: Please excuse the inline reply. EAC <br></div></div><br>