<div dir="ltr"><div><div><div>I guess a lot of companion plugins are made for outsourcing custom post types. And it is certainly better to put additional post types in a plugin rather than into the theme.<br><br></div>However, since a lot of theme companies create their own post type plugins it is still not perfect for users to keep all their content when switching themes. I would really like if there would be any standard plugins for post types (portfolio, testimonials, services) which are used by nearly every developer.<br>
<br></div>But I do not believe that the community itself will solve that problem. For me the perfect solution would be when WordPress core adds additional post types and theme authors could simply use add_theme_support() to support these post types. WordPress.com has introduced a portfolio custom post type which theme authors can utilize: <a href="http://en.support.wordpress.com/portfolios/">http://en.support.wordpress.com/portfolios/</a> <br>
</div>However, it would bloat the core and restrict use cases - and I guess that's the main reason custom post types aren't in core ;)<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-06-26 11:58 GMT+02:00 Dylan Scott <span dir="ltr"><<a href="mailto:dylan.scott@webunitydesign.com" target="_blank">dylan.scott@webunitydesign.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Just as an aside isn't having companion plugins to make themes work counter intuitive? The way I've always understood the distinction between themes and plugins is themes handle presentation and plugins handle functionality. By allowing theme authors to have companion plugins aren't you effectively tying the user to plugins? This can be especially annoying when the plugins don't work too well. Just thinking aloud and would love some other views.<br>
<br></div>Thanks<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 June 2014 01:25, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@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">Although an interesting idea, plugins can "self-deactivate" if specific conditions are met and the plugin author writes the appropriate code ... actually the plugin can do many things in many areas, but the most important point of this is simply: it is a plugin; and, as such, it really is outside the scope of the Theme Review Team to establish guidelines for plugins even if they are recommended to be used with a specific theme.<div>
<br></div><div>Personally I would prefer themes not use any "recommended plugin" method, but that would be a different discussion for a different time.</div></div><div class="gmail_extra"><br clear="all"><div>Edward Caissie<br>
aka Cais.</div>
<br><br><div class="gmail_quote"><div><div>On Wed, Jun 25, 2014 at 7:05 PM, Weaver Theme <span dir="ltr"><<a href="mailto:weavertheme@gmail.com" target="_blank">weavertheme@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<div dir="ltr"><div><div><div>As I noted in my last post, an increasing number of themes are recommending a companion support plugin to get optimal theme functionality. Some are using TGM, others other ways to load the related plugin.<br>
<br></div>My users have just reported a fairly severe issue with my own theme's companion plugin, and I've confirmed that at least some other themes with companion plugins suffer the same issue: when people deactivate a theme, they often forget to deactivate the companion plugin. This may or may not matter - but I would guess most often people would want to deactivate both the theme and its companion plugin. Since there is no deactivation hook for themes, it would be up to the plugin to detect the situation.<br>
<br></div>While it would be somewhat difficult to check and enforce, I would like to suggest that it be RECOMMENDED that companion plugins for themes detect that their "parent" theme has been deactivated, and display a notice that the plugin should be deactivated as well.<br>
<br>This sort of goes along with my suggestion that there be some more formal guidelines for theme companion plugins. It is important that the end user gets an easy and optimal experience for this increasingly common theme/companion plugin scenario.<br>
<br></div>Bruce Wampler<br></div>
<br></div></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>