<?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>Thu, 04 Dec 2008 10:33:52 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPFreaks.com: Debugging: A Beginner's guide]]></title>
      <guid>http://www.phpdeveloper.org/news/10374</guid>
      <link>http://www.phpdeveloper.org/news/10374</link>
      <description><![CDATA[<p>
On PHPFreaks.com there's a <a href="http://www.phpfreaks.com/tutorial/debugging-a-beginners-guide">new tutorial</a> providing a beginner's guide to debugging in PHP (with the built in functionality PHP has, not external software).
</p>
<blockquote>
Everyday the forums see probably hundreds of topics posted where the problem is a fairly simple error. [...] As a beginner, it can be difficult to find and solve these errors. By tackling each of these in turn, I hope to teach you some methods of finding and solving them.
</blockquote>
<p>
They look at the different sorts of errors - syntax errors, fatal errors, warnings, notices - as well as some of the ones a bit harder to track down like database problems and logical errors.
</p>]]></description>
      <pubDate>Tue, 10 Jun 2008 07:59:13 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Mindoop Blog: SEO Warning : Zend framework and duplicate content]]></title>
      <guid>http://www.phpdeveloper.org/news/9084</guid>
      <link>http://www.phpdeveloper.org/news/9084</link>
      <description><![CDATA[<p>
On the Mindoop blog, there's <a href="http://www.mindloop.be/nieuws/nieuwe-ontwikkelingen/seo-warning--zend-framework-and-duplicate-content">a new post</a> talking about some of the issues that the Zend Framework could cause with the SEO for your site - a simple reason, really.
</p>
<blockquote>
Zend framework is becoming a first choice framework for a large percentage of PHP developers. It's native support for advanced URL routing makes implementing search engine optimized URLs a breeze. Or not?
</blockquote>
<p>
Because of the reserved words for the controllers and the multiple ways to access the actions below it (his example is case_studies, case-studies and case)studies) make three different ways to get to the same content - a SEO no-no.
</p>]]></description>
      <pubDate>Wed, 21 Nov 2007 07:54:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[The Bakery: Clear the PHP4 warnings when working in eclipsePHP]]></title>
      <guid>http://www.phpdeveloper.org/news/7314</guid>
      <link>http://www.phpdeveloper.org/news/7314</link>
      <description><![CDATA[<p>
CakePHP users can find <a href="http://bakery.cakephp.org/articles/view/241">a quick hint</a> from The Bakery today pointing out how to get ride of some of the warning messages when working with the framework in PHP4.
</p>
<blockquote>
CakePHP - a great framework, but sometimes surprising to those who are used to programming with PHP 5. EclipsePHP spits out pages and pages of warnings when compiling towards a PHP 5 base, scaring new CakePHP converts.
</blockquote>
<p>
The <a href="http://bakery.cakephp.org/articles/view/241">method</a> involves performing a global search and replace on seven key strings to help them conform to the CakePHP standards. The warnings will "magically" disappear following.
</p>]]></description>
      <pubDate>Tue, 20 Feb 2007 12:47:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Pierre-Alain Joye's Blog: PEAR Template IT bugs fixes release]]></title>
      <guid>http://www.phpdeveloper.org/news/5162</guid>
      <link>http://www.phpdeveloper.org/news/5162</link>
      <description><![CDATA[<p>
<i>Pierre-Alain Joye</i> <a href="http://blog.thepimp.net/index.php/2006/04/12/56-pear-template-it-bugs-fixes-release">notes</a> today that there were some issues with the PEAR <a href="http://pear.php.net/package/HTML_Template_IT/">HTML_Template_IT</a> package he's a lead programmer for.
</p>
<quote>
<i>
<p>
An annoying bug in the ITX callback system introduced a couple of months ago has been fixed. I would force me to write 100 more tests if I forgot again to run them before a release. But the bug seems to not have affected too much people (no related bug report) :-)
</p>
<p>
The other two are a PHP notice and a warning. For some reason fread decided to raise a warning when the content is zero, it will be fixed in PHP soon, but I still have to fix it in my code.
</p>
</i>
</quote>
<p>
You can either check out the <a href="http://pear.php.net/package/HTML_Template_IT/">HTML_template_IT homepage</a> for more or just <a href="http://pear.php.net/get/HTML_Template_IT">grab it directly</a>.
</p>]]></description>
      <pubDate>Wed, 12 Apr 2006 07:37:38 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Vidyut Luther's Blog: Difference between "require()" and "include()" in PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/4611</guid>
      <link>http://www.phpdeveloper.org/news/4611</link>
      <description><![CDATA[On his blog, phpcult.com, <i>Vidyut Luther</i> talks about the difference between <a href="http://www.phpcult.com/archives/36-Difference-between-require-and-include-in-PHP.html">require and include</a> in PHP.
<p>
<quote>
<i>
This should be well known, and people should be aware as to why they are using either or. But, I've noticed lately that a lot of people new to PHP or programming are not aware of the difference. Depending on what you need you, need to decide what the differences are.
</i>
</quote>
<p>
It's a <a href="http://www.phpcult.com/archives/36-Difference-between-require-and-include-in-PHP.html">short post</a>, but for someone just getting into PHP, it's some handy information to have. He looks at both functions and gives what they're good for. He does throw in a few caveats, though - including an issue with parse errors in included files pre-PHP 4.3.5...]]></description>
      <pubDate>Thu, 05 Jan 2006 06:56:33 -0600</pubDate>
    </item>
  </channel>
</rss>
