[theme-reviewers] No hook prefix

[Chip Bennett]

I absolutely think that framework namespacing should be an obvious
exception to the namespacing guideline.

As for an author-based namespace? That gets trickier, because the potential
for a namespace clash exists since the prefix becomes arbitrary with
respect to Theme name. (The obvious example: a Theme developer who also
develops Plugins.)

How can we avoid/minimize that clash potential?

Chip

On Tue, Sep 25, 2012 at 6:27 PM, Daniel Tara <contact at onedesigns.com> wrote:

> This comes a bit as a surprise as I've always been under the impression
> that themes that use a framework are exempt from the "unique prefix" rule.
> The unique prefix per theme author seems interesting though.
>
> Daniel
>
>
> On Sep 26, 2012, at 2:20 AM, Edward Caissie wrote:
>
> 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 http://BuyNowShop.comwhere I "showcase" my themes and plugins. I still use BNS at the beginning
> of all of my plugins.
>
> This may need to be addressed on a case by case basis, but like I said,
> I'm open to discussions.
>
>
> Cais.
>
>
> On Tue, Sep 25, 2012 at 7:10 PM, Justin Tadlock <justin at justintadlock.com>wrote:
>
>> 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:
>> http://codex.wordpress.org/**Theme_Review#Theme_Namespacing<http://codex.wordpress.org/Theme_Review#Theme_Namespacing>
>>
>> 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.
>>
>> 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.
>>
>> 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?
>> ______________________________**_________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
>> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120925/b88e401b/attachment-0001.htm>