@ethan - You may also want to note you are not using the "do_settings_" functions in an initial comment on the theme ticket, and why, so the reviewer knows to look at that part of the code with an open mind.<br><br>
<br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Sat, Oct 6, 2012 at 10:02 AM, Shinra Web Holdings <span dir="ltr"><<a href="mailto:contact@shinraholdings.com" target="_blank">contact@shinraholdings.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you plan on changing the options around a lot, then having custom functions to print the pieces of your settings page makes sense. But if you're relying on do_settings_fields() for an options page, that is probably way outside your comfort zone.<br>
<br>I suggest making an array of arrays each containing the info needed for 1 option, like slug, display text, default value, input type, and options (for select and radios). Then pass this to a function that has 5 different printf's for text/textarea/checkbox/select/radio and loops through all your options.<br>
<br>If you're going to bother to do this, you also might want to consider saving all your theme settings to a single serialized option.<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">On Sat, Oct 6, 2012 at 7:11 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If you're going to create your own HTML for the settings page, then<br>
there's not much point in creating your own equivalent of the<br>
do_settings functions. Just make your own HTML in the main function.<br>
<br>
-Otto<br>
<div><div><br>
<br>
On Sat, Oct 6, 2012 at 3:52 AM, ethan anwar <<a href="mailto:ethananwar@yahoo.com" target="_blank">ethananwar@yahoo.com</a>> wrote:<br>
> Hello fellow theme reviewers!<br>
><br>
> I've got a bone to pick with the Settings API. Especially with<br>
> do_settings_sections() and do_settings_fields() .<br>
> I would like to create a more advanced Settings Page for my theme but at the<br>
> same time I'd like to stay on the safe side and use everything WordPress has<br>
> to offer.<br>
> Unfortunately WordPress has these two functions to offer and they don't<br>
> really do that much.<br>
><br>
> All that do_settings_sections() does is create a <h3> tag and a table<br>
> underneath it for do_settings_fields() to paste the options in. I'm not<br>
> happy with that.<br>
><br>
> Basically what I'm asking is "Can I create my own x_do_settings_sections()<br>
> and x_do_settings_fields() and use those instead? They will be pretty much<br>
> the same ones as the default ones declared in<br>
> wp-admin/includes/template.php, only that they'll generate a little<br>
> different HTML (divs with ID's and classes and no tables).<br>
><br>
> Thanks a lot!<br>
><br>
</div></div>> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
</blockquote></div><br>
</div></div><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></blockquote></div><br>