<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Some notices like trying to get property of
non-object and other things of that like, including reference notices could be
bad coding to something of a greater scope, and they are displayed as
notices.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>The idea is that the theme review team is really
bogged down getting all the themes reviewed, instead of weighing the individual
notices they are just blanketting all of them. </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>It also shows that the developer has been involved
with their theme to check every inconsistancy which is good coding
practice. Not to mention the deprecated messages makes sure that the
themes are developed using the current WordPress revision.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>So while I also feel the same way in some respects,
not allowing the notices/warnings/errors/deprecates is really a benefit to the
developer and the repository as a whole.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>- Phil</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=satish.iitg@gmail.com href="mailto:satish.iitg@gmail.com">Satish
Gandham</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, October 10, 2010 11:33
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] Is
WP_DEBUG really important, or is it just to take the load of ? (Satish in
reply to Chip & Phil)</DIV>
<DIV><BR></DIV>Hello Chip,<BR><BR>"Why do you say that not allowing PHP errors
and Deprecated Function Calls<BR>makes no sense?"<BR><BR>1. They are not
errors, , not even warnings they are notices.<BR><BR>It doesn't make sense
because there are somany notices from plugins and they are
harmless.<BR><BR>There may be such checks in future in plugins to, it has to
start some where and it started with themes, it's fine. Clearing those notices
should be a recommendation rather than a requirement.<BR><BR>PS: Im going to
get rid of the notices in my theme, I want my theme to be the best. I'm only
saying that a theme should not be rejected just because of those harmless
notices.<BR><BR>-----------------------<BR>Hello Phil,<BR><BR>Thanks for the
offer :), I think I can fix the errors myself.<BR><BR>Can you check the code
and UI and tell if anything can be improved further.<BR><BR>Here is the latest
version<BR><A
href="http://swiftthemes.com/Repository/SWIFT-v5.51.zip">http://swiftthemes.com/Repository/SWIFT-v5.51.zip</A><BR>---------<BR><BR>PS:
I really like the way questions are answered on this mailing list. I like the
new review team to, earlier team (may be individual) was like monarchy, the
current one is democratic :).<BR><BR>It would be great if the theme review
doesn't take 2 weeks.<BR><BR> <BR>Regards<BR>Satish Gandham<BR><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE></BODY></HTML>