[theme-reviewers] How to request "grandfathered" exception to WP 3.9 Theme guidelines?

[Bruce Wampler]

So the answer on getting a grandfathered exception is to discuss it here?

My follow up explains the problem - users with JavaScripts in the
header/footer would have them stripped from previous settings by changing
the Settings API filter.


On Thu, Mar 6, 2014 at 10:17 AM, Chip Bennett <chip at chipbennett.net> wrote:

> For which *specific* guideline (s) do you want a grandfather exception?
> On Mar 6, 2014 11:38 AM, "Bruce Wampler" <weavertheme at gmail.com> wrote:
>
>> After reviewing the impacts on my themes of the proposed 3.9 theme
>> guidelines, I've reached the conclusion that conforming to one particular
>> new requirement will seriously impact my thousands of existing users - many
>> many users would have their options simply disappear, thus breaking their
>> sites. Because of the way the Settings API work, this particular option
>> would simply be erased.
>>
>> I was working on complying when I discovered this serious problem. There
>> is no solution I can figure out to avoid existing users losing settings
>> upon update.
>>
>> How do I go about requesting getting a permanent "grandfathered"
>> exemption to one of the new guidelines for my existing themes?
>>
>> Bruce Wampler
>>
>> _______________________________________________
>> 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/20140306/4aa7c8f7/attachment-0001.html>