<?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>Tue, 18 Jun 2013 19:03:42 -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>
    <item>
      <title><![CDATA[Richard Heyes' Blog: Displaying Errors (based on hostname)]]></title>
      <guid>http://www.phpdeveloper.org/news/10142</guid>
      <link>http://www.phpdeveloper.org/news/10142</link>
      <description><![CDATA[<p>
In a response to <a href="http://php100.wordpress.com/2008/05/07/displaying-errors/">this post</a> on the PHP 10.0 Blog, <i>Richard Heyes</i> <a href="http://www.phpguru.org/#293">offers a method</a> for what <i>Stas</i> was wanting:
</p>
<blockquote>
OK, then what we do if something weird happens in production and we want to see the errors, but we don't want others to see them? [...] Maybe PHP could have some setting like display_errors=local which would enable display_errors for requests originating from developer machine but would disable it when outsider accesses it?
</blockquote>
<p>
<i>Richard</i>'s <a href="http://www.phpguru.org/#293">solution</a> checks the HTTP_HOST value of the current request and, based on whether it's marked as "live" or "dev", uses a ini_set to change the display_errors setting to true/false.
</p>]]></description>
      <pubDate>Thu, 08 May 2008 12:03:57 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[PHP 10.0 Blog: Production mode]]></title>
      <guid>http://www.phpdeveloper.org/news/6911</guid>
      <link>http://www.phpdeveloper.org/news/6911</link>
      <description><![CDATA[<p>
In an effort to get some thought going about ways to encourage security in PHP applications, <i>Stas</i> has posted <a href="http://php100.wordpress.com/2006/12/17/production-mode/">an idea</a> about a simplified php.ini setting - production=On.
</p>
<p>
His idea is that, with this setting on, the PHP installation would:
<ul> 
<li>disable display errors
<li>disable phpinfo()
<li>turn expose_php off
<li>make max_execution_time/memory_limit reasonable
<li>and possibly a few others that some developers forget to set correctly
</ul>
<a href="http://php100.wordpress.com/2006/12/17/production-mode/">Comments on the post</a> range from disagreement to suggestions on improvement and support.
</p>]]></description>
      <pubDate>Mon, 18 Dec 2006 08:43:00 -0600</pubDate>
    </item>
  </channel>
</rss>
