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

Thu Mar 6 17:29:50 UTC 2014

"Screwing" you users is only dependent on you not properly transitioning
theme settings to your plugin.
On Mar 6, 2014 12:27 PM, "Bruce Wampler" <weavertheme at gmail.com> wrote:

> So, in other words, I'm forced to screw thousands of my theme users. So be
> it.
>
> Right now, users with raw html capability can insert whatever they want,
> including JavaScript, into <head>, the header, and the footer.
>
> They've been able to do this since I introduced by theme in 2010, and
> there are thousands and thousands of users who've been using that
> capability with no know issues for all that time.
>
>
> On Thu, Mar 6, 2014 at 10:22 AM, Chip Bennett <chip at chipbennett.net>wrote:
>
>> Any arbitrary script/stylesheet that hooks into wp_head or wp_footer (or
>> that can/should do so) is exactly the focus of the guideline change.
>> Allowing a grandfather exception would defeat the purpose.
>>
>> If you're talking about markup at template locations, that's possibly
>> worth discussing.
>> On Mar 6, 2014 12:16 PM, "Bruce Wampler" <weavertheme at gmail.com> wrote:
>>
>>> I'm trying to avoid specifics on this general group, but, to
>>> generalize...
>>>
>>> Using the WP Settings API runs all settings through validation checks
>>> which often filter the content, possibly deleting part of a particular
>>> setting through the filter (think JavaScript). So, my existing
>>> validation/filters allow one kind of content to be accepted (for those with
>>> raw html capability only). The new guidelines prohibit that kind of content
>>> in some places, so to comply with the new guidelines, I would have to
>>> simply change the validation filter to remove that content. But that same
>>> filter will then also remove that content from any users who had previously
>>> had the now prohibited content. So their sites will now be broken just by
>>> updating to the new version and opening the admin page - the previously
>>> valid settings will be filtered out.
>>>
>>> A plugin (which has been suggested as a way around this requirement) is
>>> not a solution in this case because they would have to install the plugin
>>> before updating to a new 3.9 compliant version of the theme, and then
>>> simply deactivating the plugin would revert to removing the settings which
>>> is not very user friendly behavior. So the only solution I can see to not
>>> screw my exiting users is to ask to get this one thing grandfathered for my
>>> existing themes.
>>>
>>>
>>>
>>>
>>> On Thu, Mar 6, 2014 at 9:51 AM, Derek Herman <derek at valendesigns.com>wrote:
>>>
>>>> Hey Bruce,
>>>>
>>>> I just read the WordPress 3.9 proposal and didn't see anything about
>>>> settings being erased - could you please elaborate on what would cause that?
>>>>
>>>> Cheers,
>>>> Derek Herman
>>>> http://valendesigns.com
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>> _______________________________________________
>> 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/4e6b0979/attachment.html>