[theme-reviewers] Theme Options and Functions

[Edward Caissie]

To be added at WP3.1 as the latest implementation date as far as I am
concerned.
We can also look at implementing sooner as this has been noted in review
comments for the last month of two already ...
... and as we are not accepting 'child-themes' per se we can also require it
as the 'textdomain' when implementing internationalization as well.

I imagine, for future consideration, a best practices section with examples
would also be useful.


Cais.

On Wed, Oct 20, 2010 at 12:22 PM, Chip Bennett <chip at chipbennett.net> wrote:

> Awesome! Seems like we've got some consensus on that point (Theme slug as
> function/db-option prefix).
>
> Cais: something to add in the 3.1 revision?
>
> Chip
>
> On Wed, Oct 20, 2010 at 11:18 AM, Andrew Nacin <wp at andrewnacin.com> wrote:
>
>>  On Wed, Oct 20, 2010 at 12:15 PM, Bavota San <c at bavotasan.com> wrote:
>>
>>> Is a theme-slug defined in *get_theme_data()*? If so, we can suggest
>>> that developers use that so the theme-slugs remain consistent and unique to
>>> the theme.
>>>
>>
>> get_theme_data() shouldn't be used on a pageload. Way too intensive. Theme
>> slugs are rather trivial to fetch, via get_option('stylesheet') or
>> get_option('template').
>>
>>  But yes, theme-slug should be the function prefix as well as the options
>> prefix.
>>
>> _______________________________________________
>> 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/20101020/1216b381/attachment.htm>