The article is definitely going on my "Reading List" ...<br><br><div class="gmail_quote">On Fri, Feb 18, 2011 at 8:16 AM, Rahul Bansal <span dir="ltr"><<a href="mailto:rahul.bansal@rtcamp.com">rahul.bansal@rtcamp.com</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;">Length is worth the info. Didn't get time to read in detail till now.<div><br></div><div>
For ease of navigation, you may break articles into entirely different pages/posts and bind them using a series plugin.</div><div>
Other reason for this suggestion is that article in series will have their own URLs that will have advantages like:</div><div><ul><li>We can refer people to particular subtopic by sharing a unique post article</li><li>permalinks will contain keywords like "Register Settings and Define Form Sections/Fields" etc. This wil give better search engine visibility. I am less concerned about traffic gain that wil result, but my intention is to indirectly help Google give better article so developers can avoid following "wrong" article.</li>
</ul><div>Series creation may require 1-2 hours of extra time from you!</div></div><div><br></div><div>On sidenote, after taking quick overview, I felt that the article missed information about "file upload" box. (I searched "upload" keyword on "all" article page to crosscheck". Many times I find developers complaining register_settings has issues with file-uploads. </div>
<div><br></div><div>Thanks again for taking so much time to write something like this. :-)</div><div><div class="im"><br clear="all">--<br>Rahul Bansal | Founder & CEO | rtCamp Solutions Pvt. Ltd.<br>Skype: rahul286 | Twitter: @rahul286 | Web: <a href="http://rtcamp.com/" target="_blank">http://rtcamp.com/</a><br>
<br>
<br><br></div><div><div></div><div class="h5"><div class="gmail_quote">On Fri, Feb 18, 2011 at 6:27 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</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;">
Thanks!<div><br></div><div>I was worried about the length of the article, but it didn't seem to make sense to split it into multiple posts.</div><div><br></div><div>Do you think it would be useful to do a more slimmed-down follow-up post, that leaves out some of the advanced topics, like Settings page tabs, contextual help, etc.?</div>
<div><br></div><div><font color="#888888">Chip</font><div><div></div><div><br><br><div class="gmail_quote">On Fri, Feb 18, 2011 at 6:51 AM, Rahul Bansal <span dir="ltr"><<a href="mailto:rahul.bansal@rtcamp.com" target="_blank">rahul.bansal@rtcamp.com</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;">
Great article... :-)<div><br><div>Added to - <a href="http://make.wordpress.org/themes/about/resources/" target="_blank">http://make.wordpress.org/themes/about/resources/</a> (comments section)</div><div><br></div><div>Timing is good as well! 10 pages gives a lot to explore on weekend! ;-)</div>
<div><br clear="all">--<br>Rahul Bansal | Founder & CEO | rtCamp Solutions Pvt. Ltd.<br>Skype: rahul286 | Twitter: @rahul286 | Web: <a href="http://rtcamp.com/" target="_blank">http://rtcamp.com/</a><br><br>
<br><br><div class="gmail_quote"><div><div></div><div>On Fri, Feb 18, 2011 at 9:11 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div>
All,<div><br></div><div>I have just published a tutorial: <a href="http://bit.ly/hHjo6n" target="_blank">Incorporating the Settings API in WordPress Themes</a>:</div><blockquote style="margin: 0pt 0pt 0pt 40px; border: medium none; padding: 0px;">
<div><span style="color: rgb(85, 85, 85); font-family: TeXGyreScholaRegular,'URW Bookman L',Garamond,'Century Schoolbook','Bookman Old Style',Georgia,serif; font-size: 15px; line-height: 23px;"><p style="padding: 0px; margin: 2em 0px 0px; border-width: 0px;">
While others such as <a href="http://ottopress.com/2009/wordpress-settings-api-tutorial/" style="padding: 0px; margin: 0px; color: rgb(85, 136, 170); text-decoration: none; border-bottom: 1px dotted rgb(85, 136, 170); font-weight: bold;" target="_blank">Otto</a> and <a href="http://planetozh.com/blog/2009/05/handling-plugins-options-in-wordpress-28-with-register_setting/" style="padding: 0px; margin: 0px; color: rgb(85, 136, 170); text-decoration: none; border-bottom: 1px dotted rgb(85, 136, 170); font-weight: bold;" target="_blank">Ozh</a> have done yeomen's work in explaining how to implement the Settings API, I have not yet come across anything that really put everything together, and explained the process and implementation from beginning to end, in a way that even the less-experienced Theme developers (like me) could easily understand.</p>
<p style="padding: 0px; margin: 2em 0px 0px; border-width: 0px;">
This tutorial will attempt to fill that gap, by providing examples of current (as of the pending release of WordPress 3.1) best-practice implementation, not merely of the Settings API, but of Theme Options implementation as a whole, including:</p>
<ul style="padding: 0px; margin: 1em 0px 0px 10px; border-width: 0px;">
<li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">Registering options in the database as a single options array</li>
<li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">Initializing default options</li><li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">
Creating a single Theme Settings page (with tabs)</li><li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">
Defining settings page sections and fields</li><li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">
Validating and white-listing user-input form data</li><li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">
Adding Settings Page contextual help</li><li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">
Enqueueing custom CSS for the Settings page</li><li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">
Implementing settings in the Theme template files</li><li style="padding: 0px; margin: 0px 0px 0px 25px; line-height: 1.1em;">
Enqueueing front-end CSS</li></ul></span></div></blockquote><div><br></div><div>Please give it a read; I hope it is helpful. Also, any feedback, comments, corrections, criticism, etc. is welcome, so please comment!</div>
<div>
<br></div><font color="#888888"><div>Chip</div>
</font><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></blockquote></div><br></div></div>
</blockquote></div><br></div></div></div>
<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>
<br></blockquote></div><br></div></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>