[theme-reviewers] What happened here?

Emil Uzelac emil at themeid.com
Thu Mar 8 23:27:31 UTC 2012

Agreed Chip, with an exception that this was previously approved Theme ;)
But we got that cleared now.

On Thu, Mar 8, 2012 at 5:19 PM, Chip Bennett <chip at chipbennett.net> wrote:

> The reviewer was right in this case. The Theme *does* implement custom
> header and custom background, but uses a *custom* implementation, rather
> than supporting the core implementation.
> As Amy suggested, though, it would probably be best for review-specific
> comments to be left in-ticket, for posterity and for future reference for
> the Theme in question.
> Thanks,
> Chip
> On Thu, Mar 8, 2012 at 5:07 PM, Emil Uzelac <emil at themeid.com> wrote:
>> No, Theme reviewer is not and should not be disconnected from this or any
>> other ticket. Previously approved tickets should have at least 2 day grace
>> period, where reviewer will place the Theme on hold till all requirements
>> are fixed. If and when the Theme is not-approved it will not go back in #1
>> priority.
>> Theme is recommended to incorporate the following WordPress core
>> features, but is not required to do so. However, if incorporated, features
>> must support the core WordPress implementation: I hate to say this but it
>> was wrong to say that custom header, background are required.
>> For this reason only ticket should be re-opened and make sure that
>> http://codex.wordpress.org/Theme_Review#Theme_Features is followed by
>> the reviewer.
>> Cheers,
>> Emil
>> On Thu, Mar 8, 2012 at 4:56 PM, Mats Birch <birch at birchware.se> wrote:
>>> I've got a question for you, who know how these things work.
>>> I just upgraded my theme, and got a "not approved" review. I am a bit
>>> curious, because none of the things remarked upon have been changed since
>>> the previous version were approved, with no mentions of those things.
>>> How did that happen?
>>> I of course fixed, within an hour, most of it, and commented on the
>>> ticked, asking if I had done enough.
>>> I got no answer.
>>> Is that because a reviewer is disconnected from a ticket once they
>>> closed it?
>>> Anyway, I uploaded it anyway (what else to do?) and, much to my
>>> surprise, I found it in the "Priorty 3 queue", last of the last, so to
>>> speak. Wouldn't it be smoother if the reviewer could check the new one
>>> while he/she sort of knows it?
>>> The theme's last ticket is: http://themes.trac.wordpress.**
>>> org/ticket/6839 <http://themes.trac.wordpress.org/ticket/6839>
>>> ______________________________**_________________
>>> 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>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120308/c24cd415/attachment.htm>

More information about the theme-reviewers mailing list