[theme-reviewers] Theme Vs Plugin Territory

[Thomas from ThemeZee]

Thanks Chip for your quick response, I will take a look on this ;)


2013/3/1 Chip Bennett <chip at chipbennett.net>

> I would recommend using post custom meta data for querying specific posts
> to include in featured sliders. That custom post meta is specific to your
> Theme, and if the user switches Themes, both your Theme's slider and the
> custom post meta that your Theme used to query posts for the slider are
> gone - but the original user content is retained.
>
> If you use a CPT to define slider images, then when the user switches
> Themes, the underlying user content - i.e. the images themselves - are gone.
>
>
> On Fri, Mar 1, 2013 at 3:49 PM, Thomas from ThemeZee <contact at themezee.com
> > wrote:
>
>> Okay, I always thought Custom Post Types in themes are okay. I think the
>> Guidlines should clearly state that CPTs are not allowed.
>>
>> I'm currently developing a theme with a simple image slideshow and wanted
>> to use CPT for that. Since there are some themes in the directory with
>> image slideshows, can someone tell me what is the best way to include an
>> image slider?
>>
>> I mean I could use post meta keys or theme options to let users define
>> their images, but that would make no difference to CPTs. If the user
>> changes the theme he will lose that content. I understand the "generation
>> or definition of user content" is forbidden point and it makes totally
>> sense, but in my opinion defining a few images within a theme should be
>> fine. (that's more presentation than functionality).
>>
>> And using CPTs for an image slideshow seems to be the most powerful and
>> elegant way, or am I wrong??
>>
>> Best Regards,
>> Thomas
>>
>>
>> 2013/3/1 Chip Bennett <chip at chipbennett.net>
>>
>>> Custom Post Types are, by definition and design, intended for
>>> "generation or definition of user content", and as such are explicitly
>>> Plugin territory, as per the Guidelines.
>>>
>>> If a user creates content using a Theme-registered CPT, then when that
>>> user switches Themes, that content disappears. (It's there in the database,
>>> but no longer exposed to the user, either in the WordPress admin, or in the
>>> site front end; to them, that content is simply gone.) Thus, CPTs represent
>>> a form of Theme "lock-in" and are not allowed.
>>>
>>> Special-case Themes that use CPTs can be considered on a case-by-case
>>> basis.
>>>
>>>
>>> On Fri, Mar 1, 2013 at 1:43 PM, rabin shrestha <sun_ravi90 at yahoo.com>wrote:
>>>
>>>> Hi,
>>>> I am a bit of confused on theme vs plugin territory. Recently my theme
>>>> was rejected because of the use of CPT in my theme the reason was that it's
>>>> plugin territory. I know that CPT is better suited to plugin but I didn't
>>>> know that it was a required case. I have seen themes on WordPress
>>>> repository that have registered multiple CPT and being approved. I am not
>>>> saying that some X theme was approved, why not Y theme is approved for same
>>>> case. My question is,It is strictly prohibited to use CPT inside theme. Is
>>>> it a required case or is it a recommended case. If using CPT is completely
>>>> prohibited then I think writing it down on Theme review guidelines will
>>>> clear out the confusion. Though Prensentation Vs Functionality might cover
>>>> this but those words are some what vague.
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>
>> _______________________________________________
>> 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/20130301/0d01af2b/attachment.htm>