<div dir="ltr">Custom Taxonomy would fall under the same criterion, as "creation or definition of user content".</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 1, 2013 at 6:35 PM, Stephen Cui <span dir="ltr"><<a href="mailto:scui2005@gmail.com" target="_blank">scui2005@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is Custom Taxonomy allowed in theme?<br><br>Regards<span class="HOEnZb"><font color="#888888"><br><br clear="all"><div>
Stephen Cui</div></font></span><div class="HOEnZb"><div class="h5">
<br><br><div class="gmail_quote">On Fri, Mar 1, 2013 at 4:40 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">Chip-<div><br></div><div>I feel like this requirement limits the ability of themes to enable WordPress to work as a CMS for specific purposes. For instance I am working on a custom theme for a book review site that uses a CPT called books for reviews, and the regular posts for blog/news posts. I know I could have used custom post meta, but having two totally separate options (post and books) in the menus made the system super-easy for the not incredibly tech-savvy content editor on this project.</div>
<div><br></div><div>I think a generic version of this theme or something similar could be very helpful to people wanting to do a book review site. You could make a similar case for recipe blogs or other similar situations. These types of themes exist all over the place, but are pretty much excluded from the theme repository due to the user lockin. It seems to me that with some simple standards that these types of themes could be included in the repository without creating user lockin. Why not provide a way for users to have these types of very specific CMS themes with the high code standards and guaranteed GPL2 license that the theme repository provides?</div>
<div><br></div><div>Thanks,</div><div>Josh</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 1, 2013 at 1:59 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</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">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.<div>
<br></div><div>
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.</div>
<div><br></div><div>Special-case Themes that use CPTs can be considered on a case-by-case basis.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Fri, Mar 1, 2013 at 1:43 PM, rabin shrestha <span dir="ltr"><<a href="mailto:sun_ravi90@yahoo.com" target="_blank">sun_ravi90@yahoo.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><div>Hi,</div><div style="font-style:normal;font-size:13px;background-color:transparent;font-family:arial,helvetica,sans-serif">
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.<br></div></div></div><br></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>
<br></blockquote></div><br></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><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>