[theme-reviewers] Theme Options and Functions

[Muhammad Khairul Syahir Abdul Hakim]

If a theme has already stored countless rows in the database for its
options, what  do you think would be the best way to convert those to a
serialised array without needing the existing theme users to re-enter all
the options and saving them again? I'm thinking an sql update script which
the theme users must run after they update the theme. In that case what
would be the best way to notify the theme users that a database update is
required? there's no way we can output some kind of msg at the wp admin core
update screen after the update, is there?

--
Regards,
Syahir Hakim

Contact:
http://www.khairul-syahir.com
+64210333649

On 21/10/2010 5:48 AM, "Chip Bennett" <chip at chipbennett.net> wrote:

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 approachi...

_______________________________________________
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/20101021/76412bee/attachment.htm>