<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; font-size: small; "><span class="Apple-style-span" style="font-family: arial; ">On Wed, Aug 25, 2010 at 5:21 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br>
</span><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
We don't need high quality code or high quality themes.</blockquote><div> </div>On Wed, Aug 25, 2010 at 8:27 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:</span></span><div>
<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Most are failing for the basics: errors output by WP_DEBUG, invalid HTML/CSS, no wp_head() or wp_footer(), etc.</blockquote><div><span class="Apple-style-span" style="font-size: 13px; "></span><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><span class="Apple-style-span" style="border-collapse: separate;"><br>
</span></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif">Most plugins and themes output errors on WP_DEBUG. Including/especially commercial themes and the top plugins. Even though the use of notices or deprecated functions is NOT indicative of poor quality code, the simple fact is that very few of them do have quality code. A sad few.</font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><br></font></div><div><font class="Apple-style-span" face="arial, sans-serif">Akismet is quality code, yet it triggers them. So does core, on occasion. (Just visit plugins.php when running multisite, for example. And before 3.0, try using the QuickPress module -- yuck.)</font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><br></font></div><div><font class="Apple-style-span" face="arial, sans-serif">I love WP_DEBUG. I wrote an entire plugin (that most of you use) to record deprecated calls, I've written blog posts on debugging WordPress, and I cringe like the rest of you when a theme or plugin spits out errors. I've briefly looked through the theme review process. At first I loved that themes were getting a review all the way down to the notices, but I've since had some second thoughts. Rejecting a theme purely for notices or deprecated functions is a bad, bad idea, and is not the intent I had when I wrote a plugin devoted to catching them.</font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><br></font></div><div><font class="Apple-style-span" face="arial, sans-serif">Realistically, quality and education are our priorities. We cannot fail at education, or quality will suffer if only because quantity will as well. I see no problem with a theme being approved with notices/deprecated calls, if that's the only thing wrong with it.</font></div>
</div><div><font class="Apple-style-span" face="arial, sans-serif"><br></font><div><font class="Apple-style-span" face="arial, sans-serif">I believe Otto is spot on when it comes to the current deficiencies, and I do hope they are addressed.</font></div>
</div>