Yes, there was one review where that happened. But it was since corrected. We're all still learning, too.<div><br></div><div>But you specifically discussed an indictment of the review guidelines. The only thing you've mentioned is the PHP error/deprecated call requirement. Are there others?<br>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Sun, Sep 12, 2010 at 1:39 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 2:23 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">
So, you're single, greatest complaint with the guidelines is that we require no deprecated WP function calls, and no PHP errors?</blockquote><div><br></div></div><div>You asked for a specific example, not my single, greatest complaint. For that, look no further than opinions backed by expertise being rejected out of hand.</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></div>