I would say if the addition to 7) is added then the addition to 6) would less of a requirement to insure a theme is "child-able". Although best-practice coding is always a good thing to recommend.<br><br><br>Cais.<br>
<br><div class="gmail_quote">On Sat, Jan 22, 2011 at 11:49 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.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;">
<div class="im">> 6) (if) a functions.php exists, it must be compatible with the latest<br>
> version of the parent theme<br>
<br>
</div>On this note, it might be a good idea to start suggesting that all<br>
themes with functions.php files be child-able. By this, I mean that<br>
everything in the functions.php should be in a hooked function or have<br>
a if !defined / !function_exists wrapper around it. Some best<br>
practices could be drawn up.<br>
<div class="im"><br>
> 7) (if) parent theme is updated, all child themes must be updated within a<br>
> reasonable amount of time to fit with the current parent if applicable ?<br>
<br>
</div>That a reasonable question: How to handle breakage. Parents can make<br>
radical changes that will break children. Maybe create a list of<br>
themes that are "designed to be parents"? Dunno.</blockquote></div><br>