<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Top 10 Most Common Coding Mistakes in WordPress Plugins</title>
	<atom:link href="http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/feed/" rel="self" type="application/rss+xml" />
	<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/?source=rss</link>
	<description>A bit of my personal life, mainly focused on my kids. A bit of code, mainly focused on Wordpress and PHP. Overall, bits of nothing in particular.</description>
	<lastBuildDate>Wed, 23 May 2012 13:43:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Ryan</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-198044</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Tue, 08 May 2012 11:00:41 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-198044</guid>
		<description>@Ray Apologies i got the names mixed up. But you have a good point. My previous comment was directed @tdwtf. 

But still if no one is going to make an effort ill contact the author and ask him to remove the comment with his file paths. Our company got hacked a few months ago because of a developer leaving vulnerabilities open like listing the file directories. Not a nice feeling if you need to rewrite every single index.php file on our web server</description>
		<content:encoded><![CDATA[<p>@Ray Apologies i got the names mixed up. But you have a good point. My previous comment was directed @tdwtf. </p>
<p>But still if no one is going to make an effort ill contact the author and ask him to remove the comment with his file paths. Our company got hacked a few months ago because of a developer leaving vulnerabilities open like listing the file directories. Not a nice feeling if you need to rewrite every single index.php file on our web server</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ray</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-198043</link>
		<dc:creator>ray</dc:creator>
		<pubDate>Tue, 08 May 2012 10:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-198043</guid>
		<description>you&#039;re right, my choice of words could have been better but the point is still valid. Now that clearly visible error is also clearly visible in the inbox of everybody that subscribes to this post. Just sayin, you don&#039;t post somebodys filepaths on a public list.</description>
		<content:encoded><![CDATA[<p>you&#8217;re right, my choice of words could have been better but the point is still valid. Now that clearly visible error is also clearly visible in the inbox of everybody that subscribes to this post. Just sayin, you don&#8217;t post somebodys filepaths on a public list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-198042</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Tue, 08 May 2012 08:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-198042</guid>
		<description>He pointed out an error that everybody could see. Although contacting him privately would&#039; ve been a decent way to go about it but I see nothing wrong with pointing it out. Who knows maybe there was something wrong with his production server and it wasn&#039;t the same as his development server. Maybe he just needed to debug something quick. 

@Ray you cannot tell us that you never debugged on a live server before because of some strange reason that you had no choice to. If you haven&#039;t then you are not a proper programmer and just some dude that learned html and php basics</description>
		<content:encoded><![CDATA[<p>He pointed out an error that everybody could see. Although contacting him privately would&#8217; ve been a decent way to go about it but I see nothing wrong with pointing it out. Who knows maybe there was something wrong with his production server and it wasn&#8217;t the same as his development server. Maybe he just needed to debug something quick. </p>
<p>@Ray you cannot tell us that you never debugged on a live server before because of some strange reason that you had no choice to. If you haven&#8217;t then you are not a proper programmer and just some dude that learned html and php basics</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PJH</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-198041</link>
		<dc:creator>PJH</dc:creator>
		<pubDate>Tue, 08 May 2012 08:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-198041</guid>
		<description>Ray, how does pointing out a clearly visible PHP error make someone (like) a &#039;disgruntled hacker?&#039; 

Looks more like it hit a nerve and you&#039;re peeved.

Well at least you made it to TDWTF message boards.</description>
		<content:encoded><![CDATA[<p>Ray, how does pointing out a clearly visible PHP error make someone (like) a &#8216;disgruntled hacker?&#8217; </p>
<p>Looks more like it hit a nerve and you&#8217;re peeved.</p>
<p>Well at least you made it to TDWTF message boards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ray</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-198040</link>
		<dc:creator>ray</dc:creator>
		<pubDate>Mon, 07 May 2012 21:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-198040</guid>
		<description>@tdwtf
update to mistake 11
finding an error and posting it publicly instead of contacting the author privately...
doesn&#039;t make you look like some really incredible coder.
it makes you look like a disgruntled hacker who tried to hack his site and failed and now you&#039;re mad...
just sayin... think before you post
Ray</description>
		<content:encoded><![CDATA[<p>@tdwtf<br />
update to mistake 11<br />
finding an error and posting it publicly instead of contacting the author privately&#8230;<br />
doesn&#8217;t make you look like some really incredible coder.<br />
it makes you look like a disgruntled hacker who tried to hack his site and failed and now you&#8217;re mad&#8230;<br />
just sayin&#8230; think before you post<br />
Ray</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tdwtf</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-198039</link>
		<dc:creator>tdwtf</dc:creator>
		<pubDate>Mon, 07 May 2012 20:39:01 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-198039</guid>
		<description>mistake 11) displaying errors to users on a production site. From your own site:

&lt;i&gt;Warning: require_once(/home/ozh/lib/simplepie/simplepie.inc) [function.require-once]: failed to open stream: Permission denied in /home/planetozh/planetozh.com/blog/wp-content/themes/planetozh/functions-feed.php on line 56

Fatal error: require_once() [function.require]: Failed opening required &#039;/home/ozh/lib/simplepie/simplepie.inc&#039; (include_path=&#039;.:/usr/local/lib/php:/usr/local/php5/lib/pear:/home/planetozh/planetozh.com/blog/wp-content/themes/planetozh&#039;) in /home/planetozh/planetozh.com/blog/wp-content/themes/planetozh/functions-feed.php on line 56&lt;/i&gt;</description>
		<content:encoded><![CDATA[<p>mistake 11) displaying errors to users on a production site. From your own site:</p>
<p><i>Warning: require_once(/home/ozh/lib/simplepie/simplepie.inc) [function.require-once]: failed to open stream: Permission denied in /home/planetozh/planetozh.com/blog/wp-content/themes/planetozh/functions-feed.php on line 56</p>
<p>Fatal error: require_once() [function.require]: Failed opening required &#8216;/home/ozh/lib/simplepie/simplepie.inc&#8217; (include_path=&#8217;.:/usr/local/lib/php:/usr/local/php5/lib/pear:/home/planetozh/planetozh.com/blog/wp-content/themes/planetozh&#8217;) in /home/planetozh/planetozh.com/blog/wp-content/themes/planetozh/functions-feed.php on line 56</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amna</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-197780</link>
		<dc:creator>Amna</dc:creator>
		<pubDate>Wed, 22 Feb 2012 08:22:30 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-197780</guid>
		<description>Wonderful List, it will be a great help while writing plugins.</description>
		<content:encoded><![CDATA[<p>Wonderful List, it will be a great help while writing plugins.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ray</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-197713</link>
		<dc:creator>ray</dc:creator>
		<pubDate>Tue, 31 Jan 2012 00:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-197713</guid>
		<description>thanks Ozh,
Don&#039;t always think of all these things when coding so it&#039;s great to get a reminder...</description>
		<content:encoded><![CDATA[<p>thanks Ozh,<br />
Don&#8217;t always think of all these things when coding so it&#8217;s great to get a reminder&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ozh</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-197492</link>
		<dc:creator>Ozh</dc:creator>
		<pubDate>Wed, 04 Jan 2012 13:20:03 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-197492</guid>
		<description>abdussamad » Otto is saying exactly the same as me. Store 10 options in one array instead of saving one in 10 different entries. Regarding serializing, it&#039;s just how WP stores arrays.

Number 7 is still valid. You need to either implement nonces or, preferably, use the API settings, but anyway not use raw forms with no checks.</description>
		<content:encoded><![CDATA[<p>abdussamad » Otto is saying exactly the same as me. Store 10 options in one array instead of saving one in 10 different entries. Regarding serializing, it&#8217;s just how WP stores arrays.</p>
<p>Number 7 is still valid. You need to either implement nonces or, preferably, use the API settings, but anyway not use raw forms with no checks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abdussamad</title>
		<link>http://planetozh.com/blog/2009/09/top-10-most-common-coding-mistakes-in-wordpress-plugins/comment-page-2/#comment-197491</link>
		<dc:creator>abdussamad</dc:creator>
		<pubDate>Wed, 04 Jan 2012 08:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://planetozh.com/blog/?p=1321#comment-197491</guid>
		<description>Regarding 3: According to core developer otto its better to store options as an array. The reason he gives is that it saves on queries to the database:

http://lists.automattic.com/pipermail/wp-testers/2009-January/011116.html

But here you&#039;ve shown the exact opposite. Wordpress simply loads all autoload options with one DB query! So why store data as in serialized form? The memory usage is the same and it still takes just one query. Frankly I think its better to store options in separate rows. Easier to code as well.

Regarding number 7: It&#039;s now redundant with the new settings api. It does all the checking for you.</description>
		<content:encoded><![CDATA[<p>Regarding 3: According to core developer otto its better to store options as an array. The reason he gives is that it saves on queries to the database:</p>
<p><a href="http://lists.automattic.com/pipermail/wp-testers/2009-January/011116.html" rel="nofollow">http://lists.automattic.com/pipermail/wp-testers/2009-January/011116.html</a></p>
<p>But here you&#8217;ve shown the exact opposite. WordPress simply loads all autoload options with one DB query! So why store data as in serialized form? The memory usage is the same and it still takes just one query. Frankly I think its better to store options in separate rows. Easier to code as well.</p>
<p>Regarding number 7: It&#8217;s now redundant with the new settings api. It does all the checking for you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

