<?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>Sun, 06 Jul 2008 16:49:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Raphael Stolt's Blog: Zend Framework coding standards on one page]]></title>
      <guid>http://www.phpdeveloper.org/news/9610</guid>
      <link>http://www.phpdeveloper.org/news/9610</link>
      <description><![CDATA[<p>
<i>Raphael Stolt</i>, in working on his component for the Zend Framework (based on the <a href="http://pear.php.net/package/PHP_CodeSniffer">PHP_CodeSniffer</a> PEAR package), pulled together all of the information Zend provides about their coding standards into one place.
</p>
<blockquote>
Before jumping into the development of a Zend Framework coding standard for the <a href="http://pear.php.net/package/PHP_CodeSniffer">PHP_CodeSniffer</a> Pear package, I spent some time revisiting and compiling the available Zend Framework <a href="http://framework.zend.com/manual/en/coding-standard.html">coding standards</a> into a handy one-paged Pdf document.
</blockquote>
<p>
You can <a href="http://raphael.stolt.googlepages.com/ZendFramework_coding_standards_on_on.pdf">download the file here</a> or, if you want something a bit more "spread out", check out <a href="http://framework.zend.com/manual/en/coding-standard.html">the coding standards</a> on the Zend Framework website.
</p>]]></description>
      <pubDate>Tue, 12 Feb 2008 07:59:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Pierre-Alain Joye's Blog: Howto use a single php.ini for cli/cgi with htscanner, use 0.7.0 or later]]></title>
      <guid>http://www.phpdeveloper.org/news/7300</guid>
      <link>http://www.phpdeveloper.org/news/7300</link>
      <description><![CDATA[<p>
<i>Pierre-Alain Joye</i> has <a href="http://blog.thepimp.net/index.php/post/2007/02/19/Howto-use-a-single-phpini-for-cli-or-cgi-with-htscanner-use-070-or-later-%3A">posted a quick hit</a> to his blog today about using one php.ini file for both a cli and cgi installation of PHP without it throwing errors for <a href="http://pecl.php.net/htscanner">htscanner</a>.
</p>
<blockquote>
Htscanner reports error during module or request init (returns FAILURE), these errors may be fatal and stop the current executions. This behavior is not desired if you use it in a shell ((if you have only one system php.ini for both cli and cgi or if htscanner is compiled statically). This release brings a new ini settings to solve this problem, stop_on_error.
</blockquote>
<p>
The <a href="http://blog.thepimp.net/index.php/post/2007/02/19/Howto-use-a-single-phpini-for-cli-or-cgi-with-htscanner-use-070-or-later-%3A">solution</a> involves changing the htscanner setting to 0 instead of 1 to return a "SUCCESS" message rather than the errors.
</p>]]></description>
      <pubDate>Mon, 19 Feb 2007 08:58:00 -0600</pubDate>
    </item>
  </channel>
</rss>
