<div>Listing several comments from trac reviews and the theme review page:</div><div><br></div><div><div>REQUIRED: Theme options must be added to the database via a single options array, rather than separately - I know that it is a good-to-have, but I wouldn't personally reject a theme for that reason.</div>
</div><div><br></div><div>Recommended (highly) is the support of all add_theme_support features. Well, for some themes this might be obsolete. Let's take super minimalist - clean classic themes (no post thumbnails) or specifically business themes or anything else (no custom backgrounds, headers). </div>
<div><br></div><div>Our theme test data advices us, as authors and/or reviewers, to test the site with very long titles, headings, anything that could break the layout. This is normally good-to-have and very hard-to-achieve. This leads to limited design creativity actions as reviewers keep declining theme submissions by testing with a blog title with 150 characters or the super-large-title-test-post that is in the test data. </div>
<div><br></div><div>wp_link_pages and pagination hooks might not be used as well. I think that the pagination in WordPress with next/prev only is not useful and normally use custom or third-party solutions so having this as required doesn't make sense to me. Especially for a corporate/business site that doesn't even need news (pages only). SInce I've bought around 80 themes from ThemeForest for clients and friends and so, a percentage of them doesn't use news or blog.</div>
<div><br></div><div>The required CSS classes or HTML tag stylings are a common reason to reject a theme as well. .wp-caption, .wp-caption-text, .gallery-caption, .sticky, .bypostauthor are classes I add specifically for a theme before submission, never used in my demos or sites otherwise. </div>
<div><br></div><div>Some themes are rejected due to: 'this is not described in readme.txt'. We should probably define a template to be filled for every theme, for a standardization. In addition to that people won't google the markup styling for readme files, common thing for themes and plugins on WPORG.</div>
<div><br></div><div>There are other remarks as well, but these are a few I just found out. </div><div><br></div><div><br></div>A quick offtopic, this is not working:
<a href="http://themes.trac.wordpress.org/report/14">http://themes.trac.wordpress.org/report/14</a> , outputs: <div><br></div><div><div class="message" style="background-image:initial;background-color:rgb(255,255,255);border-top-width:2px;border-right-width:2px;border-bottom-width:2px;border-left-width:2px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-left-style:solid;border-top-color:rgb(221,0,0);border-right-color:rgb(221,0,0);border-bottom-color:rgb(221,0,0);border-left-color:rgb(221,0,0);color:rgb(85,0,0);padding-top:0.5em;padding-right:0.5em;padding-bottom:0.5em;padding-left:0.5em;margin-top:1em;margin-right:0px;margin-bottom:1em;margin-left:0px;font-family:Verdana,Arial,'Bitstream Vera Sans',Helvetica,sans-serif;font-size:13px">
<strong>Trac detected an internal error:</strong><pre style="margin-left:1em;overflow-x:hidden;overflow-y:hidden;white-space:normal">KeyError: 'numrows'</pre></div><br>Mario Peshev<br>Training and Consulting Services @ DevriX<br>
<a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br><a href="http://devrix.com" target="_blank">http://devrix.com</a><br><a href="http://peshev.net/blog" target="_blank">http://peshev.net/blog</a><br>
<br>
<br><br><div class="gmail_quote">On Mon, Mar 19, 2012 at 6:41 PM, 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">
I agree with all of Chip's point here ... especially the following statement:<div class="im"><br><br><div class="gmail_quote">On Mon, Mar 19, 2012 at 12:36 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ultimately, though: any discussion such as this one should include specific Guidelines that you want to see changed or removed. I'm not sure a wholesale change in philosophy is either plausible or prudent at this point.</blockquote>
</div><br></div>As much as we are open to discussing the guidelines, it is much easier to deal with specifics and review those than to take a run at the whole gamut of what the guidelines entail.<br><br><br>Cais.<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>