<div dir="ltr"><div><div><div><div><div>Okay I can see the point that the prefix should be consistent in a theme. But it is also highly comfortable for theme developers with several themes to be able to use the same function names in their themes. Since WordPress only allows to use one theme at the same time there is no conflict at all. And I'm using my shop name as prefix in all my themes, that was never a problem in reviews so far. <br>
<br></div>What's about a combination of author and theme name for unique phrases like the text domain?<br><br></div>function prefix: author-name_function<br></div>textdomain: author-name_theme-name_language<br></div>
stylesheet: author-name_theme-name_stylesheet<br><br></div>Then there would be used a consistent prefix (the author name) in the whole theme and the textdomain would also be unique.<br></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">2013/7/27 Srikanth Koneru <span dir="ltr"><<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I was hoping theme shops with a bunch of themes can get same exemption as frameworks.<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jul 27, 2013 at 6:43 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"><div dir="ltr">I would still lean towards the general rule of thumb as Theme Name ~> theme slug = prefix = textdomain to maintain a consistency within the project's code.<span><font color="#888888"><br>
</font></span></div><div class="gmail_extra"><span><font color="#888888"><br clear="all">
<div>Edward Caissie<br>aka Cais.</div></font></span><div><div>
<br><br><div class="gmail_quote">On Sat, Jul 27, 2013 at 6:55 AM, Thomas from ThemeZee <span dir="ltr"><<a href="mailto:contact@themezee.com" target="_blank">contact@themezee.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Author slug as function prefix should be fine. Beside the unique text domain the handle (name of stylesheet) used in wp_register_style should also be unique. Can cause some problems with child themes if you use the author slug there and the user has multiple themes of your theme shop installed. <br>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/27 Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">There you go :-) I was thinking that some special case Themes do that, but I was wrong.</p><div><div>
<div class="gmail_quote">On Jul 27, 2013 3:06 AM, "Otto" <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Function prefix, sure. Text domain, no. This should be unique. Prefix<br>
the text domain if you like.<br>
<br>
-Otto<br>
<br>
<br>
On Sat, Jul 27, 2013 at 1:34 AM, Srikanth Koneru <<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>> wrote:<br>
> Can the text domain and function prefix be same for all my themes and can it<br>
> possibly be my theme shop name?<br>
> It will be easy to maintain themes and create new ones.<br>
><br>
> _______________________________________________<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>
><br>
_______________________________________________<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>
</blockquote></div>
</div></div><br>_______________________________________________<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>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<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>
<br></blockquote></div><br></div></div></div>
<br>_______________________________________________<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>
<br></blockquote></div><br></div>
</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>