The reason for that review comment is that it is the current stance of the Theme Review Team that Theme functionality should involve *presentation* of data only, and that *creation* of content should be handled by Plugins. User data should not be subject to Theme "lock-in", but should be available to the user, regardless of what Theme is used.<div>
<br></div><div>The Repository/WordPress are not yet well-suited to handle "niche" Themes - though we certainly hope that both will better-accommodate such Themes in the future, given the vast potential of such Themes.</div>
<div><br></div><div>As a compromise, we are currently asking that any Theme that *creates* data (such as via a Custom Post Type) port that functionality to a Plugin (approved and available in the Plugin Repository), and use/integrate the Plugin functionality. This way, if the user switches Themes, his data are still available, since such data will be handled by the Plugin.</div>
<div><br></div><div>(Note: this requirement means that the Theme should actually be *dependent* upon the Plugin, rather than making the Plugin itself part of the Theme. It ensures that the Plugin functionality is kept current with Theme development, so that users retain access to/control of their content for as long as the developer maintains the Theme - and therefore, the Plugin.)</div>
<div><br></div><div>In the case of your Theme, porting the CPT functionality to a Plugin shouldn't be more than a 5-minute (or so) process. Then, you'll just need to ensure that the Theme checks for the Plugin being active and/or the CPT being available.</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Sun, May 29, 2011 at 1:21 PM, Diana K. Cury <span dir="ltr"><<a href="mailto:dianakac@gmail.com">dianakac@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 bgcolor="#ffffff">
<div>
<div><font face="Tahoma" size="2">Please, someone could clarify </font><a><font face="Tahoma" size="2">http://themes.trac.wordpress.org/ticket/4032</font></a></div>
<div><font face="Tahoma" size="2"></font> </div>
<div><font face="Tahoma" size="2">I'm not undertanding this:</font></div>
<blockquote dir="ltr" style="margin-right:0px">
<blockquote dir="ltr" style="margin-right:0px">
<div><em><font face="Tahoma" size="2">Even though there are a few changes to be
made I cannot approve this theme because of the implementation of custom
post types which is required to be implemented as a plugin.
(...)</font></em></div>
<div><font face="Tahoma" size="2"></font> </div></blockquote></blockquote>
<div dir="ltr" style="margin-right:0px"><font face="Tahoma" size="2">Where, who said
that post types should be implemented only as a plugin, if so, why anyone said
me tha before I re-submit the theme ten times? </font></div>
<div dir="ltr" style="margin-right:0px"><font face="Tahoma" size="2"></font> </div>
<div dir="ltr" style="margin-right:0px"><font face="Tahoma" size="2">Also, that
stands for a built in plugin or a standalone one (submit as a plugin in Plugin
Directory)?</font></div>
<div dir="ltr" style="margin-right:0px"><font face="Tahoma" size="2"></font> </div>
<div dir="ltr" style="margin-right:0px"><font face="Tahoma" size="2">Thanks,</font></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>