<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 22 May 2013 05:53:45 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Douglas Brown's Blog: Quick Methods Used for Solving PHP Errors]]></title>
      <guid>http://www.phpdeveloper.org/news/11637</guid>
      <link>http://www.phpdeveloper.org/news/11637</link>
      <description><![CDATA[<p>
<i>Douglas Brown</i> has <a href="http://www.brownphp.com/2008/12/quick-methods-used-for-solving-php-errors/">posted some hints</a> to help you find errors in your PHP scripts all centered around error reporting settings.
</p>
<blockquote>
There are several methods to solve errors in PHP code. Sometimes when the user waits to see an output a blank page will be shown if there is an error. To show the errors E_ALL^E_STRICT is used for the PHP 5 version. Contrarily, remaining versions just use E_ALL.
</blockquote>
<p>
He talks about the log_errors and display_errors settings in your php.ini, the <a href="http://php.net/error_reporting">error_reporting</a> function call or a custom error handler as shown <a href="http://us2.php.net/manual/en/function.error-reporting.php#73759">in this example</a> from the PHP manual.
</p>]]></description>
      <pubDate>Tue, 30 Dec 2008 07:57:21 -0600</pubDate>
    </item>
  </channel>
</rss>
