So, you're single, greatest complaint with the guidelines is that we require no deprecated WP function calls, and no PHP errors?<div><br></div><div>I am *absolutely* against allowing deprecated function calls, unless no alternative exists.</div>
<div><br></div><div>As for PHP errors: they're usually just indicative of overall code quality. I have yet to review a Theme that failed merely for PHP errors (or deprecated WP function calls). If we start seeing such Themes, then it would be worth another look. Besides, most PHP errors are either undeclared variables, or improperly called strings in function arguments. Both are easily correctable, and doing so isn't overly burdensome on Theme developers.</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Sun, Sep 12, 2010 at 1:09 PM, Andrew Nacin <span dir="ltr"><<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, Sep 12, 2010 at 1:20 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div>Do you have *specific* examples of onerous or unnecessary review requirements? Quite honestly, the review queue remains steady at 60+ Themes. We don't have time for navel-gazing. But if there are *specific* requirements that need to be addressed, we're always up for looking at them. (I've actually got a couple to bring up myself, regarding the Theme Unit Tests.)</div>
</div></blockquote><div><br></div></div><div>Yes. I've said previously on this list (in an email that received no replies) that I do not believe that themes should be rejected for notices and deprecated calls. This is coming from the individual who implemented deprecated argument handling, spent dozens of hours tracking down version numbers for deprecated functions, preaches WP_DEBUG [0, 1, 2], and wrote the logging plugin you use.</div>
<div><br></div><div>[0] <a href="http://www.andrewnacin.com/tag/wp_debug/" target="_blank">http://www.andrewnacin.com/tag/wp_debug/</a></div><div>[1] <a href="http://core.trac.wordpress.org/changeset/13176" target="_blank">http://core.trac.wordpress.org/changeset/13176</a></div>
<div>[2] <a href="http://core.trac.wordpress.org/changeset/13185" target="_blank">http://core.trac.wordpress.org/changeset/13185</a></div><div><br></div><div>That's not to say that theme authors shouldn't be encouraged to rectify notices on future theme submissions, or that the tolerance level shouldn't go down on successive submissions by that author. But it all depends on the notice, and it all depends on the deprecated call. If notices and deprecated calls cannot be properly evaluated for severity, then they should not be evaluated at all.</div>
</div>
<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></div>