Awesome! Seems like we've got some consensus on that point (Theme slug as function/db-option prefix).<div><br></div><div>Cais: something to add in the 3.1 revision?</div><div><br></div><div>Chip<br><br><div class="gmail_quote">
On Wed, Oct 20, 2010 at 11:18 AM, Andrew Nacin <span dir="ltr"><<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Oct 20, 2010 at 12:15 PM, Bavota San <span dir="ltr"><<a href="mailto:c@bavotasan.com" target="_blank">c@bavotasan.com</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Is a theme-slug defined in <i>get_theme_data()</i>? If so, we can suggest that developers use that so the theme-slugs remain consistent and unique to the theme.</div></blockquote><div><br>
</div></div><div>get_theme_data() shouldn't be used on a pageload. Way too intensive. Theme slugs are rather trivial to fetch, via get_option('stylesheet') or get_option('template').</div><div><br></div>
<div>
But yes, theme-slug should be the function prefix as well as the options prefix.</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></div>