<div dir="ltr">Not really; it just requires graceful degradation. Basically, the Theme works fully without the Plugin, but has *enhanced* functionality *with* the Plugin. If the user switches Themes, the Plugin is still enabled, and generated content is still available.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Mar 2, 2013 at 8:18 PM, Josh Pollock <span dir="ltr"><<a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@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">Ture, but then my theme would be dependent on my plugin. Isn't that another version of lock-in?</div>
<div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Sat, Mar 2, 2013 at 7:04 AM, Greg Priday <span dir="ltr"><<a href="mailto:greg@siteorigin.com" target="_blank">greg@siteorigin.com</a>></span> wrote:<br>
</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This guideline isn't limiting at all. If some functionality is in the<br>
plugin domain, that just means you need to move it out of your theme<br>
into a plugin. You can fully support your plugin in your theme...<br>
just make sure you gracefully degrade if it isn't installed.<br>
<br>
This is a great starting point to handling plugin dependancies -<br>
<a href="http://ottopress.com/2012/themeplugin-dependencies/" target="_blank">http://ottopress.com/2012/themeplugin-dependencies/</a><br>
<div><div><br>
On Sat, Mar 2, 2013 at 2:51 AM, Stephen Cui <<a href="mailto:scui2005@gmail.com" target="_blank">scui2005@gmail.com</a>> wrote:<br>
> The reason I ask is because Plugin has its limitation to display "user<br>
> content". Because of the limitation, I think it should be flexible on<br>
> certain gray area. Anyway, I am stick with post meta until policy changes.<br>
><br>
> Stephen<br>
><br>
><br>
> On Fri, Mar 1, 2013 at 6:26 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
>><br>
>> Custom Taxonomy would fall under the same criterion, as "creation or<br>
>> definition of user content".<br>
>><br>
>><br>
>> On Fri, Mar 1, 2013 at 6:35 PM, Stephen Cui <<a href="mailto:scui2005@gmail.com" target="_blank">scui2005@gmail.com</a>> wrote:<br>
>>><br>
>>> Is Custom Taxonomy allowed in theme?<br>
>>><br>
>>> Regards<br>
>>><br>
>>> Stephen Cui<br>
>>><br>
>>><br>
>>> On Fri, Mar 1, 2013 at 4:40 PM, Josh Pollock <<a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Chip-<br>
>>>><br>
>>>> I feel like this requirement limits the ability of themes to enable<br>
>>>> WordPress to work as a CMS for specific purposes. For instance I am working<br>
>>>> on a custom theme for a book review site that uses a CPT called books for<br>
>>>> reviews, and the regular posts for blog/news posts. I know I could have used<br>
>>>> custom post meta, but having two totally separate options (post and books)<br>
>>>> in the menus made the system super-easy for the not incredibly tech-savvy<br>
>>>> content editor on this project.<br>
>>>><br>
>>>> I think a generic version of this theme or something similar could be<br>
>>>> very helpful to people wanting to do a book review site. You could make a<br>
>>>> similar case for recipe blogs or other similar situations. These types of<br>
>>>> themes exist all over the place, but are pretty much excluded from the theme<br>
>>>> repository due to the user lockin. It seems to me that with some simple<br>
>>>> standards that these types of themes could be included in the repository<br>
>>>> without creating user lockin. Why not provide a way for users to have these<br>
>>>> types of very specific CMS themes with the high code standards and<br>
>>>> guaranteed GPL2 license that the theme repository provides?<br>
>>>><br>
>>>> Thanks,<br>
>>>> Josh<br>
>>>><br>
>>>><br>
>>>> On Fri, Mar 1, 2013 at 1:59 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> Custom Post Types are, by definition and design, intended for<br>
>>>>> "generation or definition of user content", and as such are explicitly<br>
>>>>> Plugin 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" target="_blank">sun_ravi90@yahoo.com</a>><br>
>>>>> 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 repository<br>
>>>>>> that have registered multiple CPT and being approved. I am not saying that<br>
>>>>>> some X theme was approved, why not Y theme is approved for same case. My<br>
>>>>>> question is,It is strictly prohibited to use CPT inside theme. Is it a<br>
>>>>>> 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" 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>
>>>>><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>
>>>><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>
>>><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>
>><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>
><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>
<br>
<br>
</div></div>--<br>
I make free WordPress themes<br>
<a href="http://siteorigin.com" target="_blank">http://siteorigin.com</a><br>
<a href="http://facebook.com/SiteOrigin" target="_blank">http://facebook.com/SiteOrigin</a><br>
<a href="http://twitter.com/SiteOrigin" target="_blank">http://twitter.com/SiteOrigin</a><br>
<div><div>_______________________________________________<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>
</div></div></blockquote></div></div></div><br></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>