Indeed. Our standing practice is that Themes are required to be fully functional *without* such Plugins being active. Themes can integrate support for a particular Plugin, or a Plugin can be used to *enhance* a Theme, but the Theme must function fully without such Plugins.<div>
<br></div><div>Chip<br><br><div class="gmail_quote">On Mon, Nov 7, 2011 at 6:58 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">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;">
If a theme in the WordPress Extend repository *requires* a plugin to function correctly then that functionality should be built directly into the theme itself.<br><br>Although it is an interesting piece of code you linked to, allowing for theme authors to bundle plugins that are required(?) would open the end-user to potentially unsafe code; or at the least, code that may only be reviewed when the theme is updated. As the WPTRT has no control over the code used in plugins this takes the review process out of our hands leaving the potential for unscrupulous authors to do any number of things that are not acceptable using the plugins to circumvent the Theme review process.<br>
<br>It is completely within reason for Theme authors to allow for, and use conditional code to implement, plugins to add enhanced functionality; and make recommendations of what plugins this will be best accomplished with. Thus, making them required would not be acceptable ... it is essentially saying the theme is broken, and therefore implying it should not be approved to begin with.<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote"><div class="im">On Mon, Nov 7, 2011 at 7:30 AM, Paul de Wouters <span dir="ltr"><<a href="mailto:pauldewouters@zoho.com" target="_blank">pauldewouters@zoho.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u><div><font face="Verdana, Arial, Helvetica, sans-serif">Now that it's possible to bundle custom plugins with a theme, I wonder if this raises any issues for reviewing themes with such bundled plugins that would be required for the theme to function?</font><div>
<font face="Verdana, Arial, Helvetica, sans-serif"><a href="http://thomasgriffinmedia.com/blog/2011/09/automatically-install-plugins-with-themes-for-wordpress/" target="_blank">http://thomasgriffinmedia.com/blog/2011/09/automatically-install-plugins-with-themes-for-wordpress/</a></font></div>
<div><br></div></div></blockquote></div><div><snip> <br></div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">_______________________________________________<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></div><br>
<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>