<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
This is kind of a tough one. On one hand, I would love to see themes that take advantage of custom post types in certain situations, because it provides tremendous opportunity for creativity and allows more "niche" themes that are built for specific purposes or markets to be openly accessible, however, custom post types typically rely on custom meta boxes and fields for specific information and if a user happens to switch themes, that data will most likely not be displayed correctly, such as for a "product" post type as an example. <div><br></div><div>That being said, however, there are custom post type plugins that could be supported by the theme, which would then go back to original topic. A user would still have to add the style for a custom post type if they switch themes to one that does not support the plugin natively, but at least they wouldn't have to re-create the post type in the new theme. </div><div><br></div><div>So I would agree with Chip here. Custom post types, though it would seem, in most instances, be a feature that *should* be handled by a theme, the best bet in the interest of maximum compatibility would be to add style and support for the post types within the theme, and allow a plugin to extend the theme. Again, IMO.<br><br><hr id="stopSpelling">Date: Mon, 2 May 2011 10:47:17 -0500<br>From: chip@chipbennett.net<br>To: theme-reviewers@lists.wordpress.org<br>Subject: Re: [theme-reviewers] Bundling Plugins<br><br>Themes intended for general, public distribution shouldn't be *implementing* Custom Post Types, IMHO. Custom Post Types create content, and content should maintain portability among Themes, and there is simply no good way to ensure that Theme-to-Theme naming of CPTs will be consistent.<div>
<br></div><div>I like the idea of support for "Supported Plugins", and any functional implementation that could be built around it. That's probably a very long-term goal, though.</div><div><br></div><div>Chip<br>
<br><div class="ecxgmail_quote">On Mon, May 2, 2011 at 10:20 AM, Doug Stewart <span dir="ltr"><<a href="mailto:zamoose@gmail.com">zamoose@gmail.com</a>></span> wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex">
<div class="ecxim"><br>
</div>Chip:<br>
What about Custom Post Types? If your theme implements any CPT<br>
functionality, it steps directly on that bright line.<br>
<div class="ecxim"><br>
</div>There ought to be a method for some sort of "Supports Plugins:" header<br>
tags for themes so that, as a theme installation step, an end user<br>
could specify "Download and activate all plugins marked as 'supported'<br>
in this current theme."<br>
<font color="#888888"><br>
<br>
--<br>
-Doug<br>
@zamoose<br>
<a href="http://literalbarrage.org/blog/" target="_blank">http://literalbarrage.org/blog/</a><br>
</font><div><div></div><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div>
<br>_______________________________________________
theme-reviewers mailing list
theme-reviewers@lists.wordpress.org
http://lists.wordpress.org/mailman/listinfo/theme-reviewers</div> </body>
</html>