<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi all. My theme Portfolio Press
(<a class="moz-txt-link-freetext" href="http://wordpress.org/extend/themes/portfolio-press">http://wordpress.org/extend/themes/portfolio-press</a>) is one of the
approved themes in the repository that uses custom post types. It's
been available for almost year and I've never gotten and e-mail or
support question about how to port those items to another theme-
though I do mention it in my theme FAQ and am guessing the issue
might come up at some point.<br>
<br>
I have considered putting a "Portfolio" plugin into the repository
(and would still be happy to do so), but there's a couple inherent
issues. One, even though the plugin may allow you to add new
"Portfolio" items in the backend, by switching themes you would lose
all the special attributes that actually make it display and work
like a portfolio theme. Granted, something like a "portfolio" or
"recipe" post type will still get some advantage to being called via
plugin, even if the theme is not especially equipped to handle it-
but I would think that "events" or a "bug tracker" would never
really work without theme support.<br>
<br>
SOLUTION: This might be more of a core WordPress issue. Perhaps
there could be a WordPress setting ( or core plugin ) that allows
you to select and view any custom post types you have stored in your
database. This would create the same basic functionality
generically rather than requiring each theme author to add and
maintain separate items in plugins repo.<br>
<br>
I don't think themes should be rejected on this basis until it's
been fully debated and added to the public required guidelines. I'm
also hoping my next release of Portfolio Press will make it through
the review process even while the issue is being considered.<br>
<br>
Thanks everyone!<br>
<div class="moz-signature">
<p>Devin Price<br>
WP Theming<br>
Twitter: @devinsays<br>
<a href="http://twitter.com/devinsays"></a></p>
</div>
<pre wrap="">
</pre>
</body>
</html>