[theme-reviewers] Settings API required or recommended?

[Otto]

I would very much suggest to use the theme-mod system for all cases, and
the Customizer for preference over creating an options page. The new
features in customizer where you can add Panels to contain Sections (which
themselves contain Controls) makes it possible to stuff a lot more controls
and organization in there than you might expect.

If you haven't read this yet, check it out:
https://make.wordpress.org/core/2014/07/08/customizer-improvements-in-4-0/


-Otto

On Mon, Sep 29, 2014 at 4:36 PM, Justin Tadlock <justin at justintadlock.com>
wrote:

> That specific theme was actually creating a custom table in the database,
> which is something that we wouldn't allow.  I don't think that's explicitly
> stated in the guidelines, but there's really no reason a theme should be
> creating an extra table.
>
> On Mon, Sep 29, 2014 at 3:15 PM, Srikanth Koneru <tskk79 at gmail.com> wrote:
>
>> Yes, I read your comment (
>> https://themes.trac.wordpress.org/ticket/19847#comment:30 ) so wanted to
>> know if I should say its required too.
>>
>> On Tue, Sep 30, 2014 at 1:42 AM, Justin Tadlock <justin at justintadlock.com
>> > wrote:
>>
>>> Basically, theme authors should either be using the Settings API or
>>> Theme Mods API if they're building a theme settings page.  It's not
>>> strictly required to use the Settings API, but for the majority of cases
>>> you might as well say it's a requirement because it's going to take care of
>>> a lot of problems present with custom-built theme options pages.  There
>>> are, of course, exceptions, but I don't think I've seen one yet here on
>>> WordPress.org.
>>>
>>> Ideally, we'd push theme authors to use the Theme Customizer as much as
>>> possible, which would eliminate most issues with theme options.
>>>
>>>
>>>
>>> On Mon, Sep 29, 2014 at 3:04 PM, Ulrich Pogson <grapplerulrich at gmail.com
>>> > wrote:
>>>
>>>> It is recommended but if it is not used then security precautions
>>>> should be taken.
>>>> https://make.wordpress.org/themes/handbook/guidelines/theme-security-and-privacy/#theme-settings-and-data-security
>>>>
>>>> On 29 September 2014 22:53, Srikanth Koneru <tskk79 at gmail.com> wrote:
>>>>
>>>>> Need confirmation.
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>>
>
> _______________________________________________
> 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/20140929/747d1432/attachment-0001.html>