<div dir="ltr">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.<div>
<br></div><div>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.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Mar 1, 2013 at 3:49 PM, Thomas from ThemeZee <span dir="ltr"><<a href="mailto:contact@themezee.com" target="_blank">contact@themezee.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"><div><div><div>Okay, I always thought Custom Post Types in themes are okay. I think the Guidlines should clearly state that CPTs are not allowed. <br><br></div>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?<br>
<br></div>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). <br>
<br>And using CPTs for an image slideshow seems to be the most powerful and elegant way, or am I wrong??<br><br></div>Best Regards,<br>Thomas<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br>
<div class="gmail_quote">2013/3/1 Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span><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">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>