I would tend to agree that hooks may not require custom prefixing in the same fashion as functions, classes, global variables, etc.<br><br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Mon, Mar 12, 2012 at 5:25 PM, Michael Fields <span dir="ltr"><<a href="mailto:michaelfields@automattic.com">michaelfields@automattic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">
> We currently require derivatives of Twenty Ten/Twenty Twelve to
use their own namespace for function names, hooks, etc. I see no
reason to treat Underscores derivatives any differently.<br>
<br></div>
As far as I can tell from reading
<a href="http://codex.wordpress.org/Theme_Review" target="_blank">http://codex.wordpress.org/Theme_Review</a> the use of prefixes on hooks
names is not a requirement. There are two places where prefixes are
discussed:<br>
<br>
1. Theme Namespacing: "
Themes are <b>required</b> to use a unique slug as a prefix for all
custom function names, classes, public/global variables, database
entries (Theme options, post custom metadata, etc.)
"<br>
<br>
2. Security and Privacy: "
Themes are <b>required</b> to prefix all options, custom functions,
custom variables, and custom constants with theme-slug (or
appropriate variant)."<br>
<br>
Required prefixes for hooks are not listed in either sentence.<br>
Is there another place where this is addressed?<br>
<br>
I do not believe that themes should be required to prefix all hook
names used in the theme. There are valid use-cases for not prefixing
them like plugin integration:
<a href="https://github.com/mfields/nighthawk/blob/master/category.php#L23" target="_blank">https://github.com/mfields/nighthawk/blob/master/category.php#L23</a><br>
<br>
If this was to be added to the requirements, would it be possible to
add a case-by-case clause to it somehow?<br>
</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>