I only used "based on theme author" as a point of reference, not a specific use-case. The "hybrid_" prefix would be fine as an example in this case, and meet the "based on theme author" idea I was thinking of.<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Tue, Sep 25, 2012 at 8:04 PM, 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">
I think an author based namespace goes too far, but I don't see any reason why a theme has to have just one namespace which is unique from other themes. Is there ever a situation in which two themes would be active on the same individual site at once?<div class="HOEnZb">
<div class="h5"><br>
<br><div class="gmail_quote">On Tue, Sep 25, 2012 at 6:36 PM, 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">
<div>On Tue, Sep 25, 2012 at 6:10 PM, Justin Tadlock<br>
<<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>> wrote:<br>
</div><div>> One of the things that I've wanted to do is use a standardized hook system<br>
> across all my themes. However, as per the guidelines, this is not an option<br>
> because themes require a unique prefix:<br>
> <a href="http://codex.wordpress.org/Theme_Review#Theme_Namespacing" target="_blank">http://codex.wordpress.org/Theme_Review#Theme_Namespacing</a><br>
<br>
</div>The purpose of theme namespacing is the same as that for plugin<br>
namespacing, to make sure things don't conflict with each other. In<br>
the case of themes, the fact that themes run one-per-site sorta makes<br>
that a moot point, as long as the prefix being used is careful to not<br>
conflict with plugin names and such.<br>
<br>
However, that is somewhat of a superficial viewpoint, once you<br>
consider multisite. It's conceivable that a plugin running across a<br>
multisite network could cause unintended side-effects on other sites,<br>
if their themes share hook names and the plugin references those.<br>
<br>
So, in general, I'm okay with using the same prefix across<br>
multiple-themes as long as you take that aspect into account and<br>
choose-wisely as to what your hook names are and what they are<br>
intended to do.<br>
<br>
Also, note that rules can have exceptions. I like the fact that the<br>
review team consists of real people and not just something like<br>
theme-check for that reason. That said, if theme-check is actually<br>
blocking based on this, then some clarification of the guidelines<br>
might be in order.<br>
<span><font color="#888888"><br>
-Otto<br>
</font></span><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>
</div></div></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>