[theme-reviewers] Theme Options and Functions

[Chip Bennett]

Dude, chill.

We use this mail list to discuss the process and guidelines. Just because
something is brought up here, doesn't mean that it will get implemented.
It's just being *discussed*.

FWIW, suggesting the use of an array for storing Theme options has merit. I
just went through and cleaned out literally *hundreds* of rows in
wp_options, thanks to reviewed-and-since-deleted Themes. If a Theme (or a
Plugin, for that matter - something I'll be looking into for some of my own
Plugins) has more than a couple options, it is, from a database-management
perspective, best practice to use an array, rather than discrete options.

But, again: we're just discussing these things. Nothing discussed here has
been added to the Guidelines.

Chip

On Wed, Oct 20, 2010 at 11:38 AM, Demetris Kikizas <kikizas at gmail.com>wrote:

> We are approaching a point when reading the theme guidelines will need
> more time than building a theme.
>
> I predict that people will stop bothering with reading all that
> capricious, arbitrary stuff that is put there and will stop submitting
> themes, at least people who build good themes that can become known
> without help from WordPress Extend.
>
> The worst part is that the stuff that is being continuously added to
> the guidelines does not make any sense.
>
> For example, why serialization of options should be even a recommendation?
>
> Are there any facts or measurements showing that storing 5 or 10 theme
> options in separate rows is bad in any way?
>
> I am really worried about the direction this thing has taken.
>
> Cheers,
>
> Demetris
> http://op111.net/code/wp-xo ‹ Extra Options, a practical plugin for
> WordPress
> _______________________________________________
> 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/04e61108/attachment.htm>