[theme-reviewers] quick help testing a theme

[Kirk Wight]

Aha, I did find them in the error log - I was looking in the wrong log
before, which explains my confusion. So we can presume the submitter's
environments have settings overriding the WP_DEBUG notices.

Thanks!


On 22 January 2012 17:15, Michael Fields <michael at mfields.org> wrote:

> Kirk,
>
>  I've never come across a situation like this. If the errors are not
>> always replicable, would we give the submitter the benefit of the doubt and
>> approve the theme? Or maybe require some sort of YMMV notice? Frankly, I
>> want to simply require the changes that I know will fix it for our
>> localhost situation, but that seems weird to insist a submitter change code
>> for errors that can't always be reproduced.
>>
> Both of our local installations should take precedence over the live
> server IMHO. If the theme is throwing notices and errors like this, it is
> grounds for a failure as far as I know. php.ini can be configured to log
> errors instead of displaying them inline. Have you checked the error logs
> on your live server like Simon suggested?
>
> - Mike
>
> ______________________________**_________________
> theme-reviewers mailing list
> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120122/8d33cb30/attachment-0001.htm>