Hey cant we generate shortcode from the theme itself despite using third party plugin?<br><br><div class="gmail_quote">On Sat, Mar 2, 2013 at 2:22 AM, <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: Is my theme correctly submitted? (Chip Bennett)<br>
2. Re: Theme Vs Plugin Territory (Thomas from ThemeZee)<br>
3. Re: Theme Vs Plugin Territory (Chip Bennett)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 1 Mar 2013 14:30:45 -0500<br>
From: Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
Subject: Re: [theme-reviewers] Is my theme correctly submitted?<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:CAPdLKqdy-pC3cOaorQz9%2BcUKG%2BXfj72m2ph1zFRePqJmGngfGg@mail.gmail.com">CAPdLKqdy-pC3cOaorQz9+cUKG+Xfj72m2ph1zFRePqJmGngfGg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Then I would say that the upload probably did not succeed. On a successful<br>
upload, you will see a "success" response from the uploader, and you should<br>
also receive an email indicating that a ticket has been created in<br>
Theme-Trac for your Theme. Try to upload again, and note the response from<br>
the uploader.<br>
<br>
<br>
On Fri, Mar 1, 2013 at 2:07 PM, Agentur Strau? <<br>
<a href="mailto:agentur.strauss@googlemail.com">agentur.strauss@googlemail.com</a>> wrote:<br>
<br>
> No I don't<br>
><br>
> Von meinem iPhone gesendet<br>
><br>
> Am 01.03.2013 um 20:00 schrieb Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>>:<br>
><br>
> Hi Philipp,<br>
><br>
> Did you receive an email regarding creation of a ticket in Theme-Trac?<br>
><br>
><br>
> On Fri, Mar 1, 2013 at 1:56 PM, Agentur Strau? <<br>
> <a href="mailto:agentur.strauss@googlemail.com">agentur.strauss@googlemail.com</a>> wrote:<br>
><br>
>> Hello @all, for a few Weeks I have submitted The theme named<br>
>> guenterstrauss. Was this theme correctly submitted? Best Regards<br>
>><br>
>> Philipp<br>
>><br>
>> Von meinem iPhone gesendet<br>
>><br>
>> Am 01.03.2013 um 19:36 schrieb Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>>:<br>
>><br>
>> That's always been the case, whether or not the non-GPL-compatible<br>
>> Themes/Plugins were distributed via ThemeForest or anywhere else.<br>
>><br>
>> Also, Theme URI should *not* be a TF link. Theme URI cannot be used<br>
>> solely to link to an Upsell Theme. Theme URI, if linked, must be a resource<br>
>> for the free version being hosted in the Directory.<br>
>><br>
>><br>
>> On Fri, Mar 1, 2013 at 1:11 PM, Merci Javier <<a href="mailto:mercijavier@gmail.com">mercijavier@gmail.com</a>>wrote:<br>
>><br>
>>><br>
>>><br>
>>> On Thu, Feb 28, 2013 at 7:22 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>>wrote:<br>
>>><br>
>>>> I'm going to go ahead and say that, once the 100% GPL license is<br>
>>>> available, Theme developers who use that license option for all their<br>
>>>> ThemeForest-hosted Themes/Plugins would be welcome to advertise those<br>
>>>> ThemeForest-hosted Themes/Plugins.<br>
>>>><br>
>>>> (Consider that an official statement, unless/until it is superseded by<br>
>>>> someone above the pay<br>
>>>><br>
>>><br>
>>> "all their TF hosted themes/plugins"<br>
>>> - So going forward,. if some of the author's themes are not GPL, they<br>
>>> cannot use TF theme doc link as Theme URL?<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>
>> 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>
>> 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>
> 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>
> 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/20130301/933ae2c4/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130301/933ae2c4/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 1 Mar 2013 21:49:39 +0100<br>
From: Thomas from ThemeZee <<a href="mailto:contact@themezee.com">contact@themezee.com</a>><br>
Subject: Re: [theme-reviewers] Theme Vs Plugin Territory<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
Message-ID:<br>
<CAHfybZ0PikgT5H7HhgQ0u_Tjo2dAZjs06B3xvzftEUAK9ZQ=<a href="mailto:0g@mail.gmail.com">0g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Okay, I always thought Custom Post Types in themes are okay. I think the<br>
Guidlines should clearly state that CPTs are not allowed.<br>
<br>
I'm currently developing a theme with a simple image slideshow and wanted<br>
to use CPT for that. Since there are some themes in the directory with<br>
image slideshows, can someone tell me what is the best way to include an<br>
image slider?<br>
<br>
I mean I could use post meta keys or theme options to let users define<br>
their images, but that would make no difference to CPTs. If the user<br>
changes the theme he will lose that content. I understand the "generation<br>
or definition of user content" is forbidden point and it makes totally<br>
sense, but in my opinion defining a few images within a theme should be<br>
fine. (that's more presentation than functionality).<br>
<br>
And using CPTs for an image slideshow seems to be the most powerful and<br>
elegant way, or am I wrong??<br>
<br>
Best Regards,<br>
Thomas<br>
<br>
<br>
2013/3/1 Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
<br>
> Custom Post Types are, by definition and design, intended for "generation<br>
> or definition of user content", and as such are explicitly Plugin<br>
> territory, as per the Guidelines.<br>
><br>
> If a user creates content using a Theme-registered CPT, then when that<br>
> user switches Themes, that content disappears. (It's there in the database,<br>
> but no longer exposed to the user, either in the WordPress admin, or in the<br>
> site front end; to them, that content is simply gone.) Thus, CPTs represent<br>
> a form of Theme "lock-in" and are not allowed.<br>
><br>
> Special-case Themes that use CPTs can be considered on a case-by-case<br>
> basis.<br>
><br>
><br>
> On Fri, Mar 1, 2013 at 1:43 PM, rabin shrestha <<a href="mailto:sun_ravi90@yahoo.com">sun_ravi90@yahoo.com</a>>wrote:<br>
><br>
>> Hi,<br>
>> I am a bit of confused on theme vs plugin territory. Recently my theme<br>
>> was rejected because of the use of CPT in my theme the reason was that it's<br>
>> plugin territory. I know that CPT is better suited to plugin but I didn't<br>
>> know that it was a required case. I have seen themes on WordPress<br>
>> repository that have registered multiple CPT and being approved. I am not<br>
>> saying that some X theme was approved, why not Y theme is approved for same<br>
>> case. My question is,It is strictly prohibited to use CPT inside theme. Is<br>
>> it a required case or is it a recommended case. If using CPT is completely<br>
>> prohibited then I think writing it down on Theme review guidelines will<br>
>> clear out the confusion. Though Prensentation Vs Functionality might cover<br>
>> this but those words are some what vague.<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/20130301/9291d655/attachment-0001.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130301/9291d655/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 1 Mar 2013 15:52:02 -0500<br>
From: Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
Subject: Re: [theme-reviewers] Theme Vs Plugin Territory<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:CAPdLKqcMjCsZFpf-cyH-p9TJ34o64-P-q33Lehg4FbFUQ6R%2B9g@mail.gmail.com">CAPdLKqcMjCsZFpf-cyH-p9TJ34o64-P-q33Lehg4FbFUQ6R+9g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I would recommend using post custom meta data for querying specific posts<br>
to include in featured sliders. That custom post meta is specific to your<br>
Theme, and if the user switches Themes, both your Theme's slider and the<br>
custom post meta that your Theme used to query posts for the slider are<br>
gone - but the original user content is retained.<br>
<br>
If you use a CPT to define slider images, then when the user switches<br>
Themes, the underlying user content - i.e. the images themselves - are gone.<br>
<br>
<br>
On Fri, Mar 1, 2013 at 3:49 PM, Thomas from ThemeZee<br>
<<a href="mailto:contact@themezee.com">contact@themezee.com</a>>wrote:<br>
<br>
> Okay, I always thought Custom Post Types in themes are okay. I think the<br>
> Guidlines should clearly state that CPTs are not allowed.<br>
><br>
> I'm currently developing a theme with a simple image slideshow and wanted<br>
> to use CPT for that. Since there are some themes in the directory with<br>
> image slideshows, can someone tell me what is the best way to include an<br>
> image slider?<br>
><br>
> I mean I could use post meta keys or theme options to let users define<br>
> their images, but that would make no difference to CPTs. If the user<br>
> changes the theme he will lose that content. I understand the "generation<br>
> or definition of user content" is forbidden point and it makes totally<br>
> sense, but in my opinion defining a few images within a theme should be<br>
> fine. (that's more presentation than functionality).<br>
><br>
> And using CPTs for an image slideshow seems to be the most powerful and<br>
> elegant way, or am I wrong??<br>
><br>
> Best Regards,<br>
> Thomas<br>
><br>
><br>
> 2013/3/1 Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
><br>
>> Custom Post Types are, by definition and design, intended for "generation<br>
>> or definition of user content", and as such are explicitly Plugin<br>
>> territory, as per the Guidelines.<br>
>><br>
>> If a user creates content using a Theme-registered CPT, then when that<br>
>> user switches Themes, that content disappears. (It's there in the database,<br>
>> but no longer exposed to the user, either in the WordPress admin, or in the<br>
>> site front end; to them, that content is simply gone.) Thus, CPTs represent<br>
>> a form of Theme "lock-in" and are not allowed.<br>
>><br>
>> Special-case Themes that use CPTs can be considered on a case-by-case<br>
>> basis.<br>
>><br>
>><br>
>> On Fri, Mar 1, 2013 at 1:43 PM, rabin shrestha <<a href="mailto:sun_ravi90@yahoo.com">sun_ravi90@yahoo.com</a>>wrote:<br>
>><br>
>>> Hi,<br>
>>> I am a bit of confused on theme vs plugin territory. Recently my theme<br>
>>> was rejected because of the use of CPT in my theme the reason was that it's<br>
>>> plugin territory. I know that CPT is better suited to plugin but I didn't<br>
>>> know that it was a required case. I have seen themes on WordPress<br>
>>> repository that have registered multiple CPT and being approved. I am not<br>
>>> saying that some X theme was approved, why not Y theme is approved for same<br>
>>> case. My question is,It is strictly prohibited to use CPT inside theme. Is<br>
>>> it a required case or is it a recommended case. If using CPT is completely<br>
>>> prohibited then I think writing it down on Theme review guidelines will<br>
>>> clear out the confusion. Though Prensentation Vs Functionality might cover<br>
>>> this but those words are some what vague.<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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130301/f3485ec8/attachment.htm" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130301/f3485ec8/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 18<br>
***********************************************<br>
</blockquote></div><br>