[theme-reviewers] Decaying of older themes and mass emailing users pre 3.0 to update their theme.

[Chip Bennett]

If we could implement a system like Mozilla has for Firefox add-ons, where
the add-on can't be auto-installed from the repository if it doesn't work
with the user's current version of Firefox, then I agree that suspending
wouldn't be necessary.

Ideally, we could implement something similar, integrated into the
WP-Admin, in which the "Install" button is replaced with a "Doesn't work
with your version of WordPress" notice, thereby requiring the user to
download/install the Theme manually, then that might be the best of all
worlds.

Chip

On Mon, Jun 11, 2012 at 7:29 AM, Edward Caissie <edward.caissie at gmail.com>wrote:

> @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.
>
> 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?!.
>
> 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.
>
>
> Cais.
>
>
>
> On Mon, Jun 11, 2012 at 1:26 AM, Philip M. Hofer (Frumph) <
> philip at frumph.net> wrote:
>
>> 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.
>>
>>
>>
>> -----Original Message----- From: Otto
>> Sent: Sunday, June 10, 2012 10:14 PM
>> To: theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
>> Subject: Re: [theme-reviewers] Decaying of older themes and mass emailing
>> users pre 3.0 to update their theme.
>>
>>
>> If it's not actually broken in some major way, I'm against suspending
>> it. For the moment. I'd like a better solution.
>>
>> Perhaps a flag or something to indicate that the theme is old would be
>> better, somehow.
>>
>> -Otto
>>
>>
>>
>> On Sun, Jun 10, 2012 at 11:59 PM, Chip Bennett <chip at chipbennett.net>
>> wrote:
>>
>>> I see that as something related, even required - but separate from what
>>> Phil
>>> suggests.
>>>
>>> At this point, I am in favor of suspending Themes not updated within a
>>> set
>>> time frame (1 year, 2 major WP releases, etc.).
>>>
>>> Chip
>>>
>> ______________________________**_________________
>> 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<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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120611/44fe2572/attachment.htm>