<div dir="ltr">This is probably a good time to move the discussion to the Make/Themes site:<div><a href="http://make.wordpress.org/themes/2013/02/15/child-theme-support/">http://make.wordpress.org/themes/2013/02/15/child-theme-support/</a><br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 15, 2013 at 10:20 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">That might be a bridge too far. Not all functions are *intended* by the Theme developer to be over-ridden, and requiring support for over-riding such functions may introduce considerable development complexity.<div>
<br></div><div>I could certainly see a "RECOMMENDED" for making Theme functions either filterable or pluggable, but I worry about unintended consequences of *requiring* pluggable functions.</div></div><div class="HOEnZb">
<div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, Feb 15, 2013 at 10:18 AM, Kirk Wight <span dir="ltr"><<a href="mailto:kwight@kwight.ca" target="_blank">kwight@kwight.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
How about requiring<span></span> any functions not on hooks to be pluggable?<div><div><br><br>On Friday, February 15, 2013, Edward Caissie wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Those guidelines look fine.<br>I like the idea of how a "basic" Child-Theme is spelled out, and I think you covered the use of the the `template` versus `stylesheet` usage.<br></div><div class="gmail_extra">
<br clear="all"><div>Edward Caissie<br>aka Cais.</div>
<br><br><div class="gmail_quote">On Fri, Feb 15, 2013 at 10:04 AM, Chip Bennett <span dir="ltr"><<a>chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I've taken a first-pass stab at Child Theme support guidelines. Please note that these are indicated as DRAFT ONLY, for the purpose of discussion:<div><a href="http://codex.wordpress.org/Theme_Review#Child_Theme_Support" target="_blank">http://codex.wordpress.org/Theme_Review#Child_Theme_Support</a><br>
</div><div><br></div><div>Please take a look. Feedback welcome.</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 12, 2013 at 6:20 PM, Chip Bennett <span dir="ltr"><<a>chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Support for Child Themes is certainly recommended. I would be in favor of making Child Theme-friendliness required for repository-hosted Themes, but it would be something to put up for discussion first.<div>
<br></div><div>I can't think of any reason *not* to require proper use of get_template_directory_uri() vs get_stylesheet_directory_uri(), in order to facilitate Child Theme-friendliness. But, others may think differently.</div>
<div><br></div><div>Shall I start a discussion over on Make/Themes?</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 12, 2013 at 5:26 PM, esmi at quirm dot net <span dir="ltr"><<a>esmi@quirm.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Just wondered if you had any comments on <<a href="http://wordpress.org/support/topic/not-getting-help-from-a-theme-developer" target="_blank">http://wordpress.org/support/<u></u>topic/not-getting-help-from-a-<u></u>theme-developer</a>><br>
<br>
Not so much the lack of support complaint. More the fact that the theme cannot be child-themed because of an over-use of get_stylesheet_directory_uri() instead of get_template_directory_uri() in a few places. Seems a pity that a nice theme is "spoilt" by this oversight. Given that there is a big push in the support forums to stop people editing themes in favour of using custom css plugins or child themes, should support for child themes be recommended? If not even mandatory?<br>
<br>
Mel<span><font color="#888888"><br>
-- <br>
<a href="http://quirm.net" target="_blank">http://quirm.net</a><br>
<a href="http://blackwidows.co.uk" target="_blank">http://blackwidows.co.uk</a><br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a>theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a>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>
</blockquote>
</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></blockquote></div><br></div>