<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
> 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>
As far as I can tell from reading
<a class="moz-txt-link-freetext" href="http://codex.wordpress.org/Theme_Review">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: "
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
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>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
2. Security and Privacy: "
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
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 class="moz-txt-link-freetext" href="https://github.com/mfields/nighthawk/blob/master/category.php#L23">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>
</body>
</html>