<font color="#333333"><font><font face="arial,helvetica,sans-serif">Same here, all client work is prefixed similarly, first to "separate" my codes from other developers (with specific clients) and it does make stuff easier. </font></font></font><div>
<font color="#333333"><font><font face="arial,helvetica,sans-serif"><br></font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif">IMO this should not be big issue, but as Cais said, let's discuss :)</font></font></font><div>
<font color="#333333"><font><font face="arial,helvetica,sans-serif"><br></font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif">Thanks,</font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif">Emil<br>
</font></font></font><br><div class="gmail_quote">On Tue, Sep 25, 2012 at 6:20 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would be open to discussing a prefix based on the theme author, especially one with multiple themes in the repository. For the longest time I was using bns_ as the prefix of choice (all of my themes use a more "unique" prefix now, but the code is otherwise almost identical for these items) as it also keeps in line with my "brand" at <a href="http://BuyNowShop.com" target="_blank">http://BuyNowShop.com</a> where I "showcase" my themes and plugins. I still use BNS at the beginning of all of my plugins.<br>
<br>This may need to be addressed on a case by case basis, but like I said, I'm open to discussions.<br><br><br clear="all">Cais.<div class="HOEnZb"><div class="h5"><br>
<br><br><div class="gmail_quote">On Tue, Sep 25, 2012 at 7:10 PM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
One of the things that I've wanted to do is use a standardized hook system across all my themes. However, as per the guidelines, this is not an option because themes require a unique prefix:<br>
<a href="http://codex.wordpress.org/Theme_Review#Theme_Namespacing" target="_blank">http://codex.wordpress.org/<u></u>Theme_Review#Theme_Namespacing</a><br>
<br>
All my themes are built on the same framework as well as several themes from other theme authors (some of which are also on .ORG). Trying to explain why the "hybrid_before_content" hook won't work with the Prototype theme is problematic with many of my users. As I build more themes, I can see this becoming an even bigger issue.<br>
<br>
The biggest thing for me is cutting back on repeat support questions. I'll have one user find a perfectly good answer in my forums for another theme that won't work with the theme he's using.<br>
<br>
I don't see not having a unique prefix on hooks as a major issue. But, I wanted to touch base with you all before going down this route with my themes. Thoughts?<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</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></div></div>