<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Add this to functions.php:<div><br></div><div>remove_filter( 'the_excerpt', 'wpautop' );<br><div><div><br></div><div>Daniel</div><div><br></div><div>On Mar 5, 2013, at 10:23 PM, priyanshu mittal wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hey please help me <br><br>How can we remove paragraph tags from excerpt i m only want the text of excerpt how can i do this?<br><br><div class="gmail_quote">On Tue, Mar 5, 2013 at 9:55 PM, <span dir="ltr"><<a href="mailto:theme-reviewers-request@lists.wordpress.org" target="_blank">theme-reviewers-request@lists.wordpress.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send theme-reviewers mailing list submissions to<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:theme-reviewers-request@lists.wordpress.org">theme-reviewers-request@lists.wordpress.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:theme-reviewers-owner@lists.wordpress.org">theme-reviewers-owner@lists.wordpress.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of theme-reviewers digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Queue Push Update (Otto)<br>
2. Re: Denied From Commercial List (Otto)<br>
3. Re: Drop-in code library and public namespace (Slobodan Manic)<br>
4. Re: Plugin dependencies (misunderstanding) (hal-android)<br>
5. Re: Drop-in code library and public namespace (Chip Bennett)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 5 Mar 2013 07:50:08 -0600<br>
From: Otto <<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>><br>
Subject: Re: [theme-reviewers] Queue Push Update<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
Message-ID:<br>
<CAD-Fghw=<a href="mailto:Msscn_SKxeWxXVmC2pGOvuW3gv2Gj8D0eQXRn49qBA@mail.gmail.com">Msscn_SKxeWxXVmC2pGOvuW3gv2Gj8D0eQXRn49qBA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
It is indeed case-sensitive, however his username really is "Shelob9",<br>
with the capital S.<br>
<br>
I suggest that you clear cookies and make sure you log in with the<br>
capital letters.<br>
<br>
-Otto<br>
<br>
<br>
On Mon, Mar 4, 2013 at 8:05 PM, Josh Pollock <<a href="mailto:jpollock412@gmail.com">jpollock412@gmail.com</a>> wrote:<br>
> Sorry. Works now. I will do an extra theme review as penance.<br>
><br>
><br>
> On Mon, Mar 4, 2013 at 8:29 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
>><br>
>> The name is case-sensitive. Last time, you said "Shelob9". :)<br>
>><br>
>><br>
>> On Mon, Mar 4, 2013 at 8:27 PM, Josh Pollock <<a href="mailto:jpollock412@gmail.com">jpollock412@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Still doesn't work. Can someone verify that I got added to the reviews<br>
>>> group? My username is shelob9<br>
>>><br>
>>> Thanks!<br>
>>><br>
>>><br>
>>> On Mon, Mar 4, 2013 at 7:27 PM, Srikanth Koneru <<a href="mailto:tskk79@gmail.com">tskk79@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Modify ticket should work, try logging out and log back in once.<br>
>>>><br>
>>>><br>
>>>> On Tue, Mar 5, 2013 at 5:55 AM, Josh Pollock <<a href="mailto:jpollock412@gmail.com">jpollock412@gmail.com</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> Maybe I'm missing something obvious, but hwo do I assign myself a<br>
>>>>> theme? I thought I could do it from modify ticket, but when I tried this on<br>
>>>>> an unassigned theme the only option available is "leave as new".<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On Mon, Mar 4, 2013 at 12:01 AM, Josh Pollock <<a href="mailto:jpollock412@gmail.com">jpollock412@gmail.com</a>><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>> Thanks Chip!<br>
>>>>>><br>
>>>>>><br>
>>>>>> On Sun, Mar 3, 2013 at 11:47 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
>>>>>> wrote:<br>
>>>>>>><br>
>>>>>>> You're added to the "reviewers" group now. Feel free to assign/close<br>
>>>>>>> tickets yourself. :)<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On Sun, Mar 3, 2013 at 11:16 PM, Josh Pollock <<a href="mailto:jpollock412@gmail.com">jpollock412@gmail.com</a>><br>
>>>>>>> wrote:<br>
>>>>>>>><br>
>>>>>>>> I reviewed 1 theme twice (he resubmitted after my original<br>
>>>>>>>> recommendation and the default widget debate.) The second ticket is #1139<br>
>>>>>>>> (<a href="http://themes.trac.wordpress.org/ticket/11399" target="_blank">http://themes.trac.wordpress.org/ticket/11399</a>), which I recommended be<br>
>>>>>>>> approved but is still open.<br>
>>>>>>>><br>
>>>>>>>> My username is Shelob9.<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> On Sun, Mar 3, 2013 at 10:38 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
>>>>>>>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>> You're welcome to do as many as you would like or are able to do.<br>
>>>>>>>>> :) How many have you done now, and what's your username?<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> On Sun, Mar 3, 2013 at 10:15 PM, Josh Pollock<br>
>>>>>>>>> <<a href="mailto:jpollock412@gmail.com">jpollock412@gmail.com</a>> wrote:<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> I know that I'm still an egg, but I could commit to doing 2 this<br>
>>>>>>>>>> week if you feel that I'm ready for that at this stage in my training.<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> On Sun, Mar 3, 2013 at 3:26 PM, Chip Bennett<br>
>>>>>>>>>> <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
>>>>>>>>>>><br>
>>>>>>>>>>> We're down to only 14 tickets older than 2 weeks:<br>
>>>>>>>>>>> <a href="http://themes.trac.wordpress.org/report/3" target="_blank">http://themes.trac.wordpress.org/report/3</a><br>
>>>>>>>>>>><br>
>>>>>>>>>>> Anyone available to wipe out the Priority #2 queue?<br>
>>>>>>>>>>><br>
>>>>>>>>>>> Overall, we're down to 76 total tickets waiting to be reviewed,<br>
>>>>>>>>>>> with 217 tickets closed in the past 7 days:<br>
>>>>>>>>>>> <a href="http://themes.trac.wordpress.org/" target="_blank">http://themes.trac.wordpress.org/</a><br>
>>>>>>>>>>><br>
>>>>>>>>>>> Nice work so far, everyone!<br>
>>>>>>>>>>><br>
>>>>>>>>>>> Chip<br>
>>>>>>>>>>><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>
>>>>>>>>>><br>
>>>>>>>>>><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>
>>>>>>>>><br>
>>>>>>>>><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>
>>>>>>>><br>
>>>>>>>><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>
>>>>>>><br>
>>>>>>><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>
>>>>>><br>
>>>>><br>
>>>>><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>
>>>><br>
>>>><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>
>>><br>
>>><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>
>><br>
>><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>
><br>
><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>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 5 Mar 2013 08:09:39 -0600<br>
From: Otto <<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>><br>
Subject: Re: [theme-reviewers] Denied From Commercial List<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
Message-ID:<br>
<<a href="mailto:CAD-Fghz951fMOmUSo1q9jOH7hmiCMg2a0-hO2jrp6fx8zQnkGg@mail.gmail.com">CAD-Fghz951fMOmUSo1q9jOH7hmiCMg2a0-hO2jrp6fx8zQnkGg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Tue, Mar 5, 2013 at 6:46 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> Just briefly catching up with this thread. I think, at the very least, if<br>
> "have at least 3 Themes available" is an acceptance criterion, it should be<br>
> included in this list:<br>
<br>
The commercial listing is currently undergoing a revamp. You may<br>
notice that the list is smaller than it was before and many new sites<br>
got added (a bunch more got removed).<br>
<br>
Also, the "list" of criteria given on that page is not meant to be an<br>
exhaustive list, nor is it set in stone. It will change as time goes<br>
on.<br>
<br>
However, I do agree that a commercial vendor with only one theme does<br>
not qualify to be on that list. I would not set the limit of number of<br>
themes at any arbitrary point, such as "3", but clearly "1" is too<br>
few. Here's another unlisted criteria, for example: "You have to be an<br>
established theme vendor." Anybody could throw up a website and sell<br>
themes in a matter of about 30 minutes. Do they get on the list too?<br>
<br>
<a href="http://WordPress.org">WordPress.org</a> and the people working on it will decide the contents of<br>
that page using terms and criteria that we feel best helps out our<br>
user-base and gives an accurate portrayal of the state of commercial<br>
themes, as well as promotes the best theme-shops we can find. You're<br>
free to argue about the decisions all you like, but they will continue<br>
to be made using the criteria we feel are best.<br>
<br>
-Otto<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 5 Mar 2013 17:19:04 +0100<br>
From: Slobodan Manic <<a href="mailto:slobodan.manic@gmail.com">slobodan.manic@gmail.com</a>><br>
Subject: Re: [theme-reviewers] Drop-in code library and public<br>
namespace<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
Message-ID:<br>
<CAN27JAkC5JCLibB5EGLgg0UKd=<a href="mailto:310bB5bJU374ewoHrvh93a8Q@mail.gmail.com">310bB5bJU374ewoHrvh93a8Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Thanks to everyone who chimed in.<br>
<br>
I will definitely add notes on theme's usage of Customizer Boilerplate<br>
before submitting the updated version.<br>
<br>
Also, it's only function prefixes that are different and relevant. There's<br>
also an array of sample options in this file in Customizer<br>
Boilerplate<<a href="https://github.com/slobodan/WordPress-Theme-Customizer-Boilerplate/blob/master/customizer-boilerplate/options.php" target="_blank">https://github.com/slobodan/WordPress-Theme-Customizer-Boilerplate/blob/master/customizer-boilerplate/options.php</a>>,<br>
"using" 'my_theme_textdomain' translation string, but those are just sample<br>
options and are not meant to be translated, but simply overwriten in themes<br>
function.php file.<br>
<br>
---<br>
<br>
Slobodan Manic<br>
WordPress developer at *ThematoSoup* <<a href="http://thematosoup.com/" target="_blank">http://thematosoup.com/</a>><br>
Twitter: *@slobodanmanic* <<a href="https://twitter.com/#!/slobodanmanic" target="_blank">https://twitter.com/#!/slobodanmanic</a>><br>
<br>
<br>
<br>
On Tue, Mar 5, 2013 at 2:32 PM, Edward Caissie <<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>>wrote:<br>
<br>
> The premise behind the namespace guidelines are to help insure a few<br>
> things, one being theme uniqueness.<br>
> In this case, given the "drop-in" and the theme are by the same<br>
> author, the issue of namespace clashing should be moot.<br>
><br>
> I would be able to accept this namespace difference, perhaps adding a<br>
> note to the theme's documentation explaining the difference /<br>
> relevance would be helpful.<br>
><br>
> Also, as noted by @Daniel, this issue has already been addressed and<br>
> "drop-in" libraries are fine to use, especially since this one appears<br>
> to use a unique prefix as its namespace.<br>
><br>
><br>
> Edward Caissie<br>
> aka Cais.<br>
><br>
><br>
> On Tue, Mar 5, 2013 at 3:21 AM, Abhik Biswas <<a href="mailto:abhik@itsabhik.com">abhik@itsabhik.com</a>> wrote:<br>
> > I must have missed that.<br>
> ><br>
> ><br>
> > On Tue, Mar 5, 2013 at 1:39 PM, Daniel Tara <<a href="mailto:contact@onedesigns.com">contact@onedesigns.com</a>><br>
> wrote:<br>
> >><br>
> >> That is not true. Frameworks are allowed to be used unaltered; that's he<br>
> >> whole point of using frameworks anyway. This has been discussed before<br>
> >> (several times) and has been deemed acceptable. See here:<br>
> >><br>
> >><br>
> <a href="http://make.wordpress.org/themes/2012/03/14/theme-frameworks-and-namespacing-guidelines/" target="_blank">http://make.wordpress.org/themes/2012/03/14/theme-frameworks-and-namespacing-guidelines/</a><br>
> >><br>
> >> Daniel<br>
> >><br>
> >> On Mar 5, 2013, at 8:45 AM, Abhik Biswas wrote:<br>
> >><br>
> >> As long as I know, themes are *required* to use its name's slug as the<br>
> >> callback prefixes. Therefore, if you are using a prefix that's not your<br>
> >> theme's name slug, might colide with other callbacks. Also, all the<br>
> callback<br>
> >> prefixes in a theme should be same and unique. You can not use different<br>
> >> prefixes in a single theme.<br>
> >><br>
> >> A veteran reviwer can clarify it better than me.<br>
> >><br>
> >> _______________________________________________<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>
> >><br>
> >><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>
> ><br>
> ><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>
> _______________________________________________<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130305/2baa36ab/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130305/2baa36ab/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 5 Mar 2013 23:20:18 +0700<br>
From: hal-android <<a href="mailto:hasilent00@gmail.com">hasilent00@gmail.com</a>><br>
Subject: Re: [theme-reviewers] Plugin dependencies (misunderstanding)<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
Message-ID:<br>
<CAJ3vVhPdf01aG0f=<a href="mailto:pw27521uByPppSoGZyYGd6imw-NgPtOAog@mail.gmail.com">pw27521uByPppSoGZyYGd6imw-NgPtOAog@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
@Chipbennet<br>
Thank you very much, for the answer.<br>
I will review that theme right away.<br>
<br>
Best regards<br>
Hendro Prayitno<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 5 Mar 2013 11:25:05 -0500<br>
From: Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
Subject: Re: [theme-reviewers] Drop-in code library and public<br>
namespace<br>
To: "[theme-reviewers]" <<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>><br>
Message-ID:<br>
<<a href="mailto:CAPdLKqevOEN-4KFRJ4LW-1BAjRQG%2BCyXPEcdXEv8ZqFimrd9hw@mail.gmail.com">CAPdLKqevOEN-4KFRJ4LW-1BAjRQG+CyXPEcdXEv8ZqFimrd9hw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Right. We do need to use common sense here. :) If "placeholder" functions<br>
intended to be filtered is properly filtered, such that the actual<br>
namespacing used is correct, then there's no reason to fail the<br>
"placeholder" functions. (The propriety of such "placeholder" code is<br>
debatable, but IMHO outside of our scope.)<br>
<br>
<br>
On Tue, Mar 5, 2013 at 11:19 AM, Slobodan Manic <<a href="mailto:slobodan.manic@gmail.com">slobodan.manic@gmail.com</a>>wrote:<br>
<br>
> Thanks to everyone who chimed in.<br>
><br>
> I will definitely add notes on theme's usage of Customizer Boilerplate<br>
> before submitting the updated version.<br>
><br>
> Also, it's only function prefixes that are different and relevant. There's<br>
> also an array of sample options in this file in Customizer Boilerplate<<a href="https://github.com/slobodan/WordPress-Theme-Customizer-Boilerplate/blob/master/customizer-boilerplate/options.php" target="_blank">https://github.com/slobodan/WordPress-Theme-Customizer-Boilerplate/blob/master/customizer-boilerplate/options.php</a>>,<br>
> "using" 'my_theme_textdomain' translation string, but those are just sample<br>
> options and are not meant to be translated, but simply overwriten in themes<br>
> function.php file.<br>
><br>
> ---<br>
><br>
> Slobodan Manic<br>
> WordPress developer at *ThematoSoup* <<a href="http://thematosoup.com/" target="_blank">http://thematosoup.com/</a>><br>
> Twitter: *@slobodanmanic* <<a href="https://twitter.com/#!/slobodanmanic" target="_blank">https://twitter.com/#!/slobodanmanic</a>><br>
><br>
><br>
><br>
> On Tue, Mar 5, 2013 at 2:32 PM, Edward Caissie <<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>>wrote:<br>
><br>
>> The premise behind the namespace guidelines are to help insure a few<br>
>> things, one being theme uniqueness.<br>
>> In this case, given the "drop-in" and the theme are by the same<br>
>> author, the issue of namespace clashing should be moot.<br>
>><br>
>> I would be able to accept this namespace difference, perhaps adding a<br>
>> note to the theme's documentation explaining the difference /<br>
>> relevance would be helpful.<br>
>><br>
>> Also, as noted by @Daniel, this issue has already been addressed and<br>
>> "drop-in" libraries are fine to use, especially since this one appears<br>
>> to use a unique prefix as its namespace.<br>
>><br>
>><br>
>> Edward Caissie<br>
>> aka Cais.<br>
>><br>
>><br>
>> On Tue, Mar 5, 2013 at 3:21 AM, Abhik Biswas <<a href="mailto:abhik@itsabhik.com">abhik@itsabhik.com</a>> wrote:<br>
>> > I must have missed that.<br>
>> ><br>
>> ><br>
>> > On Tue, Mar 5, 2013 at 1:39 PM, Daniel Tara <<a href="mailto:contact@onedesigns.com">contact@onedesigns.com</a>><br>
>> wrote:<br>
>> >><br>
>> >> That is not true. Frameworks are allowed to be used unaltered; that's<br>
>> he<br>
>> >> whole point of using frameworks anyway. This has been discussed before<br>
>> >> (several times) and has been deemed acceptable. See here:<br>
>> >><br>
>> >><br>
>> <a href="http://make.wordpress.org/themes/2012/03/14/theme-frameworks-and-namespacing-guidelines/" target="_blank">http://make.wordpress.org/themes/2012/03/14/theme-frameworks-and-namespacing-guidelines/</a><br>
>> >><br>
>> >> Daniel<br>
>> >><br>
>> >> On Mar 5, 2013, at 8:45 AM, Abhik Biswas wrote:<br>
>> >><br>
>> >> As long as I know, themes are *required* to use its name's slug as the<br>
>> >> callback prefixes. Therefore, if you are using a prefix that's not<br>
>> your<br>
>> >> theme's name slug, might colide with other callbacks. Also, all the<br>
>> callback<br>
>> >> prefixes in a theme should be same and unique. You can not use<br>
>> different<br>
>> >> prefixes in a single theme.<br>
>> >><br>
>> >> A veteran reviwer can clarify it better than me.<br>
>> >><br>
>> >> _______________________________________________<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>
>> >><br>
>> >><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>
>> ><br>
>> ><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>
>> _______________________________________________<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>
><br>
><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>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130305/ae5c5dd3/attachment.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130305/ae5c5dd3/attachment.htm</a>><br>
<br>
------------------------------<br>
<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>
<br>
End of theme-reviewers Digest, Vol 34, Issue 84<br>
***********************************************<br>
</blockquote></div><br>
_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<br></blockquote></div><br></div></body></html>