I believe a WP theme should also have an option to delete the database entries made by it so that there is no data left by a theme when the user wants to remove it completely. I have tried to incorporate it in Shaan WP theme.<br>
<br>Maybe, this should be made mandatory to help users keep their databases tidy.<br><br>Rgds,<br>Pritam<br><br><div class="gmail_quote">On Fri, Jan 7, 2011 at 5:30 PM, <span dir="ltr"><<a href="mailto:theme-reviewers-request@lists.wordpress.org">theme-reviewers-request@lists.wordpress.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Send theme-reviewers mailing list submissions to<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:theme-reviewers-request@lists.wordpress.org">theme-reviewers-request@lists.wordpress.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:theme-reviewers-owner@lists.wordpress.org">theme-reviewers-owner@lists.wordpress.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of theme-reviewers digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Article on how to create a Theme Options Page for<br>
WordPress (Chip Bennett)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 7 Jan 2011 05:42:08 -0600<br>
From: Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
Subject: Re: [theme-reviewers] Article on how to create a Theme<br>
Options Page for WordPress<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
Message-ID:<br>
<<a href="mailto:AANLkTinZ5toprc8-MtcB8%2BGUQEwH7F3gtgHOH7EWUc1J@mail.gmail.com">AANLkTinZ5toprc8-MtcB8+GUQEwH7F3gtgHOH7EWUc1J@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Best practice (and most importantly, the *accepted* best practice with<br>
respect to WordPress Themes) is to put all options in an array:<br>
<br>
1) It protects your options from potential conflict (which is another point:<br>
you didn't prefix your options names with "theme-slug")<br>
2) It makes white-listing much easier<br>
3) It makes manipulating options much easier<br>
4) It makes removing options from the DB much easier<br>
5) It makes reading the DB much easier<br>
<br>
(I'm sure there are more.)<br>
<br>
*Any* tutorials put out by the Theme Review Team should be consistent on<br>
matters of guidelines and best practices. There are some conventions that I<br>
don't personally like, either - but for the sake of standardization (and not<br>
creating confusion), I put aside my personal preferences.<br>
<br>
Chip<br>
<br>
On Fri, Jan 7, 2011 at 1:26 AM, Daniel Tara <<a href="mailto:contact@onedesigns.com">contact@onedesigns.com</a>> wrote:<br>
<br>
> By the way, I personally don?t like having all the options in a single<br>
> registered array. It?s ugly to call for a global variable?s array key<br>
> instead of the option directly and it?s confusing to give the name for a<br>
> HTML input field arrayname[arraykey]. Just my 2 cents on this.<br>
><br>
><br>
><br>
> Daniel<br>
><br>
><br>
><br>
> *From:* <a href="mailto:theme-reviewers-bounces@lists.wordpress.org">theme-reviewers-bounces@lists.wordpress.org</a> [mailto:<br>
> <a href="mailto:theme-reviewers-bounces@lists.wordpress.org">theme-reviewers-bounces@lists.wordpress.org</a>] *On Behalf Of *Daniel Tara<br>
> *Sent:* Friday, January 07, 2011 9:22 AM<br>
><br>
> *To:* <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
> *Subject:* Re: [theme-reviewers] Article on how to create a Theme Options<br>
> Page for WordPress<br>
><br>
><br>
><br>
> Thanks for the feedback,<br>
><br>
><br>
><br>
> I corrected the grammar errors, changed the capability to<br>
> ?edit_theme_options?, rewritten some portions where I omitted things and<br>
> bundled the entire code into a child theme for Twenty Ten, which I tested<br>
> and is working.<br>
><br>
><br>
><br>
> Daniel<br>
><br>
><br>
><br>
> *From:* <a href="mailto:theme-reviewers-bounces@lists.wordpress.org">theme-reviewers-bounces@lists.wordpress.org</a> [mailto:<br>
> <a href="mailto:theme-reviewers-bounces@lists.wordpress.org">theme-reviewers-bounces@lists.wordpress.org</a>] *On Behalf Of *Edward Caissie<br>
> *Sent:* Thursday, January 06, 2011 3:42 PM<br>
> *To:* <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
> *Subject:* Re: [theme-reviewers] Article on how to create a Theme Options<br>
> Page for WordPress<br>
><br>
><br>
><br>
> There are a few minor typos and a grammar issue or two, otherwise ... I<br>
> believe the capability should be 'edit_theme_options' versus<br>
> 'manage_options' based on Justin Tadlock's discussions.<br>
><br>
> Good Read! Definitely adds more insight into the Settings API.<br>
><br>
><br>
><br>
> Cais.<br>
><br>
> PS: The first time I clicked on the link it took me to the page, every<br>
> other time I click or use the URL (copy&paste) it wants to open my feed<br>
> reader ... EAC<br>
><br>
> On Wed, Jan 5, 2011 at 11:12 PM, Daniel Tara <<a href="mailto:contact@onedesigns.com">contact@onedesigns.com</a>><br>
> wrote:<br>
><br>
> Thought I make this public,<br>
><br>
><br>
><br>
> Here?s an article on how to create options pages for WordPress themes using<br>
> the Settings API<br>
><br>
><br>
><br>
><br>
> <a href="http://www.onedesigns.com/tutorials/how-to-create-a-wordpress-theme-options-page" target="_blank">http://www.onedesigns.com/tutorials/how-to-create-a-wordpress-theme-options-page</a><br>
><br>
><br>
><br>
> I would appreciate any feedback as I probably missed some things out.<br>
><br>
><br>
><br>
> Daniel<br>
><br>
><br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20110107/7c4d1a32/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20110107/7c4d1a32/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br>
<br>
End of theme-reviewers Digest, Vol 8, Issue 28<br>
**********************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Regards,<br>
Pritam<br>98103-98014<br><br>