<?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>Sat, 18 May 2013 15:55:36 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Gonzalo Ayuso's Blog: Display errors on screen even with display errors = off with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/16977</guid>
      <link>http://www.phpdeveloper.org/news/16977</link>
      <description><![CDATA[<p>
<i>Gonzalo Ayuso</i> has posted a handy tip to his blog today about <a href="http://gonzalo123.wordpress.com/2011/10/10/display-errors-on-screen-even-with-display-errors-off-in-php/">showing errors even with "display_errors" being off</a> in your application (could be helpful in debugging those difficult problems).
</p>
<blockquote>
 Shared hosting are cheap, but normally they don't allow us the use some kind of features. For example we cannot see the error log. That's a problem when we need to see what happens within our application. Normally I work with my own servers, and I have got full access to error logs. But if we cannot see the error log and the server is configured with <a href="http://es.php.net/manual/en/errorfunc.configuration.php#ini.display-errors">display errors = off</a> in php.ini (typical configuration in shared hosting), we have a problem.
</blockquote>
<p>
His solution involves an "error sniffer" script that captures the issues in a script and echoes them out at the end. In <a href="https://github.com/gonzalo123/ErrorSniffer">his ErrorSniffer</a> he sets up a custom error, exception and shutdown handler to grab the problems and capture them for later use - including echoing them out to the user if desired.
</p>]]></description>
      <pubDate>Tue, 11 Oct 2011 11:03:07 -0500</pubDate>
    </item>
  </channel>
</rss>
