<?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, 21 May 2013 02:43:00 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Proof Group's Blog:  Know Your PHP Environments]]></title>
      <guid>http://www.phpdeveloper.org/news/13650</guid>
      <link>http://www.phpdeveloper.org/news/13650</link>
      <description><![CDATA[<p>
On the Proof Group's blog there's <a href="http://proofgroup.com/blog/2009/dec/know_your_php_environments">a recent post</a> about a "gotcha" <i>Andy Chase</i> found when using the <a href="http://drupal.org/project/drush">Drush</a> command line tool for Drupal installations and a system that has <a href="http://mamp.info/">MAMP</a> installed.
</p>
<blockquote>
Recently, however, I installed <a href="http://mamp.info/">MAMP</a> to debug some older, PHP4-specific code. [...] I also use <a href="http://drupal.org/project/drush">Drush</a>, which is an indispensable Drupal command line tool, and I began getting the following error on some sites: Drush command could not be completed. 
</blockquote>
<p>
This only caused a problem when he went back to his previous PHP5-based installation. He finally found the culprit - a section of the Drush script that looked for MAMP installs and tried to use those binaries and configuration files (the PHP4 ones) instead of his more correct PHP5 ones. A quick commenting later everything worked fine.
</p>]]></description>
      <pubDate>Wed, 09 Dec 2009 13:10:17 -0600</pubDate>
    </item>
  </channel>
</rss>
