<div dir="ltr"><div><div>I skipped your ticket because it was complex for me and moved on to next tickets. You will have to wait for a more experienced reviewer. <br></div>The neuro ticket is not a stumbling block and not the reason for your ticket being not reviewed yet.<br>
</div>Also don't reply to digests :)<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 15, 2013 at 1:31 PM, Nicolas GUILLAUME <span dir="ltr"><<a href="mailto:nguillaume@gmail.com" target="_blank">nguillaume@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>@reviewers : what is the exact priority rule for already approved theme : it seems that some tickets are sometimes reviewed and approved before older ones. Is it related to the complexity of the ticket or, are there some other rules to be aware of?<br>
</div><div>Thank you for your answers.</div><div><br></div>@Emil Uzelac : correct me if I am wrong but from my understanding, tickets are addressed in a chronological order, from the oldest to the newest. To deblock the queue, this ticket should then be treated in first : <a href="http://themes.trac.wordpress.org/ticket/13131" target="_blank">http://themes.trac.wordpress.org/ticket/13131</a>.<u> It has been reopened 3 weeks ago by Chip Bennett but the developer did not answer Chip's question since then.</u><div>
<br><div>In my case, the ticket is this one : <a href="http://themes.trac.wordpress.org/ticket/13241" target="_blank">http://themes.trac.wordpress.org/ticket/13241</a>. I made many improvements in the code and I can't wait to see it live!</div>
<div><br></div><div>Cheers,</div><div>Nicolas.<br><div><br></div><div><br></div><div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/15 <span dir="ltr"><<a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank">theme-reviewers-request@lists.wordpress.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Send theme-reviewers mailing list submissions to<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank">theme-reviewers-request@lists.wordpress.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:theme-reviewers-owner@lists.wordpress.org" target="_blank">theme-reviewers-owner@lists.wordpress.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of theme-reviewers digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Webmaster Tools IDs - plugin territory? (Emil Uzelac)<br>
2. Re: Webmaster Tools IDs - plugin territory?<br>
(Philip M. Hofer (Frumph))<br>
3. Priority #1 track list seems to be stopped (Nicolas GUILLAUME)<br>
4. Re: Priority #1 track list seems to be stopped (Emil Uzelac)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 14 Jul 2013 19:59:23 -0500<br>
From: Emil Uzelac <<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>><br>
To: "Discussion list for WordPress theme reviewers."<br>
<<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>><br>
Subject: Re: [theme-reviewers] Webmaster Tools IDs - plugin territory?<br>
Message-ID:<br>
<<a href="mailto:CAEytdhevbPu39fVfjMe6Rh4E1m0TDDP-tCFms8sckgKMrAvCqA@mail.gmail.com" target="_blank">CAEytdhevbPu39fVfjMe6Rh4E1m0TDDP-tCFms8sckgKMrAvCqA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
No worries, it's all good. So here it is, one example:<br>
<a href="http://codex.wordpress.org/Settings_API" target="_blank">http://codex.wordpress.org/Settings_API</a> excluding "Cowboy Coding"<br>
there should not be any issues with that.<br>
<br>
Or even better:<br>
<a href="https://codex.wordpress.org/Theme_Customization_API" target="_blank">https://codex.wordpress.org/Theme_Customization_API</a><br>
<br>
<br>
<br>
On Sun, Jul 14, 2013 at 7:55 PM, Azizur Rahman <<a href="mailto:prodevstudio@gmail.com" target="_blank">prodevstudio@gmail.com</a>>wrote:<br>
<br>
> If there is no core api for this kind of option/configuration then how<br>
> does a developer add those properly? (I am not picking on you Emil so don't<br>
> take it personally)<br>
><br>
> IMO these options are equivalent to robot.txt which is taken care of in<br>
> core.<br>
><br>
> In my view these are site configuration and theme should stay out of them.<br>
> It has nothing to do with presentation.<br>
><br>
> WPTRT could propose that if a theme is going to provide an interface to<br>
> set these value they need to be stores such a way that it can transfer<br>
> from theme to theme and even plugins. WPTRT needs provide those guidelines<br>
> in where and how these config stored/retrived. so that user/site is not impacted<br>
> adversely when switching themes.<br>
><br>
> I know not everyone will agree to above but it is in the best interest of<br>
> the end user.<br>
><br>
> Regards,<br>
><br>
> Azizur<br>
><br>
><br>
><br>
> On Monday, 15 July 2013, Emil Uzelac wrote:<br>
><br>
>> Hi Jason,<br>
>><br>
>> Assuming that we're referring to Theme Options, this should be fine.<br>
>><br>
>> *As long as this is not hardcoded and properly added :)*<br>
>><br>
>> Thanks,<br>
>> Emil<br>
>><br>
>><br>
>> On Sun, Jul 14, 2013 at 6:28 PM, Jason Clarke <<a href="mailto:jgc@jasonclarke.org" target="_blank">jgc@jasonclarke.org</a>>wrote:<br>
>><br>
>>> Hi Admins,<br>
>>><br>
>>> Long-time listener, first-time caller here- in reviewing my first theme,<br>
>>> I remembered a recent list discussion on how Analytics-specific fields in<br>
>>> themes are not allowed because they're considered plugin territory.<br>
>>><br>
>>> On a related note, I'm assuming that other similar fields such as<br>
>>> "Google Webmaster Tools ID" and "Alexa ID" are also plugin territory- can<br>
>>> the admins confirm this is the case?<br>
>>><br>
>>> Thank you!<br>
>>> Jason<br>
>>><br>
>>> PS - As a side/related note, it would be super helpful if the list<br>
>>> archives where somehow searchable - that might be one more avenue for<br>
>>> newbies like myself to check before emailing the list (assuming guidelines<br>
>>> haven't changed).<br>
>>><br>
>>> --<br>
>>> Jason Clarke<br>
>>> <a href="http://jasonclarke.org" target="_blank">http://jasonclarke.org</a><br>
>>><br>
>>> ************************<br>
>>><br>
>>> _______________________________________________<br>
>>> theme-reviewers mailing list<br>
>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
>>><br>
>><br>
><br>
> --<br>
> Sent from Gmail Mobile<br>
><br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130714/3ce1bd48/attachment-0001.html" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130714/3ce1bd48/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sun, 14 Jul 2013 22:52:17 -0700<br>
From: "Philip M. Hofer \(Frumph\)" <<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</a>><br>
To: "Discussion list for WordPress theme reviewers."<br>
<<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>><br>
Subject: Re: [theme-reviewers] Webmaster Tools IDs - plugin territory?<br>
Message-ID: <B338F0A4D6B7404597E3A9EDB487E426@furious><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
There are two sides of the fence on this subject, those who feel that themes should not include anything that a plugin can do; which is fine. There?s really nothing wrong with that method of thinking. The OTHER side, which includes myself and Emil and a bunch of others do not really think that it?s a necessity to police those particular things. A theme doesn?t have to be cross compatible in every way except the way that the theme unit looks. Any extra feature to a theme is just that, a bonus. Whether someone switches theme?s constantly makes no difference.<br>
<br>
A HUGE majority of themes that are being used are actually commercial themes: <a href="http://wordpress.org/themes/commercial/" target="_blank">http://wordpress.org/themes/commercial/</a><br>
<br>
Those when switching to one theme or another will have some things no longer work ? and that is fine. There are plenty of ways, avenues and programming that you can take to include those features into the theme you switch to.<br>
<br>
The BIGGEST idea about that the don?t-worry-about-it group?s main objective is to make the theme review process easier and faster to get through. The biggest thing that people get hung up on returning day after day to review themes is how time consuming they are to go through. We also believe that it?s not the theme review team?s responsibility to control that aspect of allowing a theme to have a feature or not, that is up to the core dev?s to make that determination.<br>
<br>
Use all of the plugins, theme unit test and requirements for the backlinks and other things. Do the cursory views of everything that?s important and move em through the review process.<br>
<br>
<br>
<br>
From: Emil Uzelac<br>
Sent: Sunday, July 14, 2013 5:59 PM<br>
To: Discussion list for WordPress theme reviewers.<br>
Subject: Re: [theme-reviewers] Webmaster Tools IDs - plugin territory?<br>
<br>
No worries, it's all good. So here it is, one example:<br>
<a href="http://codex.wordpress.org/Settings_API" target="_blank">http://codex.wordpress.org/Settings_API</a> excluding "Cowboy Coding"<br>
there should not be any issues with that.<br>
<br>
Or even better:<br>
<a href="https://codex.wordpress.org/Theme_Customization_API" target="_blank">https://codex.wordpress.org/Theme_Customization_API</a><br>
<br>
<br>
<br>
<br>
<br>
On Sun, Jul 14, 2013 at 7:55 PM, Azizur Rahman <<a href="mailto:prodevstudio@gmail.com" target="_blank">prodevstudio@gmail.com</a>> wrote:<br>
<br>
If there is no core api for this kind of option/configuration then how does a developer add those properly? (I am not picking on you Emil so don't take it personally)<br>
<br>
IMO these options are equivalent to robot.txt which is taken care of in core.<br>
<br>
In my view these are site configuration and theme should stay out of them. It has nothing to do with presentation.<br>
<br>
WPTRT could propose that if a theme is going to provide an interface to set these value they need to be stores such a way that it can transfer from theme to theme and even plugins. WPTRT needs provide those guidelines in where and how these config stored/retrived. so that user/site is not impacted adversely when switching themes.<br>
<br>
<br>
I know not everyone will agree to above but it is in the best interest of the end user.<br>
<br>
Regards,<br>
<br>
Azizur<br>
<br>
<br>
<br>
On Monday, 15 July 2013, Emil Uzelac wrote:<br>
<br>
Hi Jason,<br>
<br>
Assuming that we're referring to Theme Options, this should be fine.<br>
<br>
As long as this is not hardcoded and properly added :)<br>
<br>
Thanks,<br>
Emil<br>
<br>
<br>
<br>
On Sun, Jul 14, 2013 at 6:28 PM, Jason Clarke <<a href="mailto:jgc@jasonclarke.org" target="_blank">jgc@jasonclarke.org</a>> wrote:<br>
<br>
Hi Admins,<br>
<br>
Long-time listener, first-time caller here- in reviewing my first theme, I remembered a recent list discussion on how Analytics-specific fields in themes are not allowed because they're considered plugin territory.<br>
<br>
On a related note, I'm assuming that other similar fields such as "Google Webmaster Tools ID" and "Alexa ID" are also plugin territory- can the admins confirm this is the case?<br>
<br>
Thank you!<br>
Jason<br>
<br>
PS - As a side/related note, it would be super helpful if the list archives where somehow searchable - that might be one more avenue for newbies like myself to check before emailing the list (assuming guidelines haven't changed).<br>
<br>
<br>
--<br>
Jason Clarke<br>
<a href="http://jasonclarke.org" target="_blank">http://jasonclarke.org</a><br>
<br>
************************<br>
<br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
<br>
<br>
<br>
<br>
--<br>
Sent from Gmail Mobile<br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
<br>
<br>
<br>
<br>
--------------------------------------------------------------------------------<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130714/273c87f7/attachment-0001.html" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130714/273c87f7/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 15 Jul 2013 08:43:57 +0200<br>
From: Nicolas GUILLAUME <<a href="mailto:nguillaume@gmail.com" target="_blank">nguillaume@gmail.com</a>><br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
Subject: [theme-reviewers] Priority #1 track list seems to be stopped<br>
Message-ID: <<a href="mailto:51E39A2D.40107@gmail.com" target="_blank">51E39A2D.40107@gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hi,<br>
<br>
There are some tickets older than 7 days in the list (including the<br>
ticket for my theme Customizr).<br>
<br>
I can see that the top of the list ticket is reopened since 3 weeks and<br>
seems to lock all other tickets...<br>
<br>
Is there an issue there? Could somebody please take care of that?<br>
Thanks and best regards,<br>
Nicolas<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Mon, 15 Jul 2013 01:48:05 -0500<br>
From: Emil Uzelac <<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>><br>
To: "Discussion list for WordPress theme reviewers."<br>
<<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>><br>
Subject: Re: [theme-reviewers] Priority #1 track list seems to be<br>
stopped<br>
Message-ID:<br>
<CAEytdhfbdKQT-o0fumAA36i8=<a href="mailto:o%2BqguTrC%2Bn1ChzLiUB8_JdUng@mail.gmail.com" target="_blank">o+qguTrC+n1ChzLiUB8_JdUng@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
What needs to be done?<br>
On Jul 15, 2013 1:44 AM, "Nicolas GUILLAUME" <<a href="mailto:nguillaume@gmail.com" target="_blank">nguillaume@gmail.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> There are some tickets older than 7 days in the list (including the ticket<br>
> for my theme Customizr).<br>
><br>
> I can see that the top of the list ticket is reopened since 3 weeks and<br>
> seems to lock all other tickets...<br>
><br>
> Is there an issue there? Could somebody please take care of that?<br>
> Thanks and best regards,<br>
> Nicolas<br>
> ______________________________**_________________<br>
> theme-reviewers mailing list<br>
> theme-reviewers@lists.**<a href="http://wordpress.org" target="_blank">wordpress.org</a><<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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><<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130715/cb88feaf/attachment.html" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130715/cb88feaf/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
<br>
------------------------------<br>
<br>
End of theme-reviewers Digest, Vol 38, Issue 72<br>
***********************************************<br>
</blockquote></div><br></div></div></div></div></div></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>