@Amy - Thanks for the support (*grin*) although I imagine the patch I wrote will need to be revisited with the new WP_Theme API in place.<br><br>As to the discussion in general, I agree with Otto on not suspending a theme without good cause and being old is not good enough. Failing miserably on security or some other serious issue is obviously justifiable, but as noted, if the entire theme uses deprecated functions they still exist and the theme will "work" to the best of my knowledge ... it's just not recommended to use?!.<br>
<br>I know I made suggestions in the past and we have gone round and round a few times trying to come up with a working solution ... those discussions were what prompted the patch that @Amy noted to be submitted. Once/if that patch is added, then a REQUIRED guideline to make those details be included with new submissions and down the road those themes can be simply (and possibly much more easily) flagged as out of date or untested. Even existing themes can be noted as untested until they have been updated with this key information. This in itself may be the impetus needed to bring the repository as a whole in to a more current status.<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Mon, Jun 11, 2012 at 1:26 AM, Philip M. Hofer (Frumph) <span dir="ltr"><<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That's what I was referring to earlier. Someone mentioned that last time we had this discussion. A "disclaimer" one that is seen from the installed WordPress as well as the repo.<br>
<br>
<br>
<br>
-----Original Message----- From: Otto<br>
Sent: Sunday, June 10, 2012 10:14 PM<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
Subject: Re: [theme-reviewers] Decaying of older themes and mass emailing users pre 3.0 to update their theme.<div class="HOEnZb"><div class="h5"><br>
<br>
If it's not actually broken in some major way, I'm against suspending<br>
it. For the moment. I'd like a better solution.<br>
<br>
Perhaps a flag or something to indicate that the theme is old would be<br>
better, somehow.<br>
<br>
-Otto<br>
<br>
<br>
<br>
On Sun, Jun 10, 2012 at 11:59 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I see that as something related, even required - but separate from what Phil<br>
suggests.<br>
<br>
At this point, I am in favor of suspending Themes not updated within a set<br>
time frame (1 year, 2 major WP releases, etc.).<br>
<br>
Chip<br>
</blockquote>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a> <br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</div></div></blockquote></div><br>