<?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, 08 Jul 2008 23:04:37 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPImpact Blog: Symfony's plugins tell us a lot about what developers need]]></title>
      <guid>http://www.phpdeveloper.org/news/10466</guid>
      <link>http://www.phpdeveloper.org/news/10466</link>
      <description><![CDATA[<p>
The PHP::Impact blog has <a href="http://phpimpact.wordpress.com/2008/06/21/symfonys-plugins-tell-us-a-lot-about-what-developers-need/">a new post</a> that overviews the plugin system that the <a href="http://www.symfony.org">Symfony</a> framework has to offer.
</p>
<blockquote>
If you want to use the power of the Rails framework without having to learn Ruby, then Symfony is the right framework for you. After spending more than 10 months playing around with Rails, I can say that Symfony is a great alternative to Rails for programmers who already know PHP. 
</blockquote>
<p>
He talks about what a plugin is, how its used by the framework, the simple installation process and a "top ten" list of some of the most popular plugins (including <a href="http://trac.symfony-project.com/trac/wiki/sfGuardPlugin">sfGuardPlugin</a>, <a href="http://trac.symfony-project.com/trac/wiki/sfSimpleForumPlugin">sfSimpleForm</a> and <a href="http://trac.symfony-project.com/trac/wiki/sfControlPanelPlugin">sfControlPanel</a>).
</p>]]></description>
      <pubDate>Mon, 23 Jun 2008 14:33:35 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[IBM developerWorks: Debugging PHP using Eclipse and PDT]]></title>
      <guid>http://www.phpdeveloper.org/news/10435</guid>
      <link>http://www.phpdeveloper.org/news/10435</link>
      <description><![CDATA[<p>
The IBM developerWorks website has a <a href="http://www.ibm.com/developerworks/edu/os-dw-os-php-eclipse-pdt-debug.html?S_TACT=105AGX59&S_CMP=GRsite-btw01&ca=dgr-btw01EclipsePDTDebug">new tutorial</a> (login required) showing how to use the Eclipse PDT functionality to debug scripts your PHP development.
</p>
<blockquote>
The PHP Development Tools (PDT) plug-in, when installed with Eclipse Europa, gives you that ability to quickly write and debug PHP scripts and pages. PDT supports two debugging tools: XDebug and the Zend Debugger. Learn how to configure PDT for debugging PHP scripts and discover which perspectives you use when taking closer looks at your scripts. 
</blockquote>
<p>
You'll need to have a machine with PHP, Eclipse, Apache and the PHP Development Tools already installed to follow along (as well as a trial version of the Zend Studio Web Debugger). They also include the methods for setting up <a href="http://www.xdebug.de">XDebug</a> as the debugger.
</p>]]></description>
      <pubDate>Wed, 18 Jun 2008 11:17:13 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Symfony Blog: How do I use Propel 1.3 in symfony 1.1?]]></title>
      <guid>http://www.phpdeveloper.org/news/10311</guid>
      <link>http://www.phpdeveloper.org/news/10311</link>
      <description><![CDATA[<p>
A new post over on the Symfony blog today show how to <a href="http://www.symfony-project.org/blog/2008/05/30/how-do-i-use-propel-1-3-in-symfony-1-1">combine the framework</a> with the <a href="http://propel.phpdb.org/trac/wiki/Users/Documentation/1.3">Propel</a> templating system thanks to some new enhancements.
</p>
<blockquote>
Starting with <a href="http://www.symfony-project.org/blog/2008/05/07/symfony-1-1-0-rc1-is-out">symfony 1.1</a>, it is now possible to easily use <a href="http://propel.phpdb.org/trac/wiki/Users/Documentation/1.3">Propel 1.3</a> in your project to take advantage of its speed improvements, nested set implementation, object instance pooling, among others. Most importantly, Propel 1.3 uses PDO instead of Creole as the DBAL, offering a significant performance boost.
</blockquote>
<p>
There's a few steps to getting everything all set up, but they're pretty simple. First, you'll need to grab the right plugin from the Symfony repository, then you change the yml file configuration for the PDO connection, change a few settings in your propel.ini and clear the cache and rebuild the models - you're all set! (Complete commands and example configurations are included)
</p>]]></description>
      <pubDate>Fri, 30 May 2008 16:12:31 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPImpact Blog: 20 MediaWiki Extensions You Should Be Using]]></title>
      <guid>http://www.phpdeveloper.org/news/10258</guid>
      <link>http://www.phpdeveloper.org/news/10258</link>
      <description><![CDATA[<p>
If you're a MediaWiki user, the PHP::Impact blog has a list of <a href="http://phpimpact.wordpress.com/2008/03/08/20-mediawiki-extensions-you-should-be-using/">twenty extensions</a> you don't want to miss out on:
</p>
<blockquote>
MediaWiki is a great PHP-based Wiki application that is used to power many sites, including Wikipedia itself. One of MediaWiki strengths is how easy it is to extend with its plug-in architecture. The following is a list of 20 extensions that should make your life easier and save you a fair bit of time. 
</blockquote>
<p>Plugins included in the list are things like:</p>
<ul>
<li><a href="http://www.mediawiki.org/wiki/Extension:SimpleFeed">SimpleFeed</a>
<li><a href="http://www.mediawiki.org/wiki/Extension:Tasks_Extension">Tasks</a>
<li><a href="http://www.mediawiki.org/wiki/Extension:CheckUser">CheckUser</a>
<li><a href="http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi">SyntaxHighlight GeSHi</a>
</ul>
<p>
Check out <a href="http://phpimpact.wordpress.com/2008/03/08/20-mediawiki-extensions-you-should-be-using/">the full list</a> for more great plugins.
</p>]]></description>
      <pubDate>Fri, 23 May 2008 12:57:06 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Shantanu Goel's Blog:  Migrating From PHP4 To PHP5: Solving WP-Cache (and maybe other) Issues]]></title>
      <guid>http://www.phpdeveloper.org/news/10091</guid>
      <link>http://www.phpdeveloper.org/news/10091</link>
      <description><![CDATA[<p>
If you're a WordPress user and are in the process of an upgrade from PHP4 to PHP5, you might be having a few issues. One problem can be cause by the wp-cache component and <a href="http://tech.shantanugoel.com/2008/04/07/migrating-from-php4-to-php5-solving-wp-cache-and-maybe-other-issues.html">this recent post</a> from <i>Shantanu Goel</i>.
</p>
<blockquote>
The issues range from weird page layouts, to some controls not working, to some errors popping up here and there, and probably your blog not even displaying. This occurs because even though WordPress is PHP5 compatible, some of the plugins you are using might not be.
</blockquote>
<p>
In his case, it was the wp-cache plugin that was causing the problems. Permissions weren't right to allow it to do its job. This resulted in problems rendering content and with the site acting as it normally would. His solution involved disabling and reenabling the plugin after deleting the cache and lock file the plugin uses.
</p>]]></description>
      <pubDate>Thu, 01 May 2008 14:23:33 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[C7Y: Reflections on Designing an IRC Bot in PHP, Part 2]]></title>
      <guid>http://www.phpdeveloper.org/news/9996</guid>
      <link>http://www.phpdeveloper.org/news/9996</link>
      <description><![CDATA[<p>
<i>Matthew Turland</i> notes that the <a href="http://c7y.phparch.com/c/entry/1/art,irc_bots_in_php2">second part</a> of his "IRC Bots in PHP" series of articles has been posted to the C7Y community site (from <a href="http://www.phparch.com">php|architect</a>).
</p>
<blockquote>
The precursor to this article introduced some background and an overview of the design for the Phergie project as an example of the concepts involved in a PHP IRC bot implementation. This article will go further into the topic of plugins including descriptions of those that are commonly needed to make a bot fully functional as well as the commonly needed core features to support plugin development.
</blockquote>
<p>
In <a href="http://www.phpdeveloper.org/news/9934">part one</a> he set up some of the foundation code and explained some of the thought behind the structure of the bot. In <a href="http://c7y.phparch.com/c/entry/1/art,irc_bots_in_php2">this part</a> he gets more into the heart of the bot, showing how to define functions for common IRC actions (join/part/ping/etc) and how he made a plugin system to handle custom actions. He also mentions topics like memory usage, data storage methods and some of the "niceties" he included.
</p>]]></description>
      <pubDate>Fri, 18 Apr 2008 11:14:56 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Symfony Blog:  Upgrade your plugins]]></title>
      <guid>http://www.phpdeveloper.org/news/9831</guid>
      <link>http://www.phpdeveloper.org/news/9831</link>
      <description><![CDATA[<p>
The Symfony project is recommending you <a href="http://www.symfony-project.org/blog/2008/03/18/upgrade-your-plugins">upgrade your plugins</a> to the latest editions - an issue with the PEAR channel caused it to load the wrong ones:
</p>
<blockquote>
A problem in the symfony project PEAR channel made the plugin-install task always install the oldest version of the plugins, instead of the latest. If you recently installed plugins with the symfony command line, you probably installed an outdated version. Plugins installed via SVN are not affected.
</blockquote>
<p>
You'll need to run a plugin-upgrade command for each of the plugins installed on your system to ensure that you're completely up to date. The <a href="http://www.symfony-project.org/blog/2008/03/18/upgrade-your-plugins">post</a> has complete info on how to tell which plugins you have and the exact commands to issue to being them up to date.
</p>]]></description>
      <pubDate>Thu, 20 Mar 2008 12:03:06 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Matthew Turland's Blog: Meet Phergie]]></title>
      <guid>http://www.phpdeveloper.org/news/9697</guid>
      <link>http://www.phpdeveloper.org/news/9697</link>
      <description><![CDATA[<p>
<i>Matthew Turland</i> has been working on a project based on an idea he and <i>Ben Ramsey</i> thought up - a wrapper around the <a href="http://libircclient.sourceforge.net/">libircclient</a> libraries to make IRC interface simple. As a result, <i>Matthew</i> turned it into a more practical application - you can call her <a href="http://ishouldbecoding.com/2008/02/20/meet-phergie/">Phergie</a>.
</p>
<blockquote>
I had toyed with some previous iterations of Phergie, some Python-based and later some PHP-based, before I finally got an API design I was happy with.
</blockquote>
<p>
The source for the bot can be downloaded from its <a href="http://svn2.assembla.com/svn/phergie/">subversion repository</a> and you can find out more about it on its <a href="http://trac2.assembla.com/phergie">Trac site</a>. Also, if you feel like chatting about it, you can head over to the #phergie channel on the <a href="http://www.freenode.org">Freenode IRC network</a>.
</p>]]></description>
      <pubDate>Mon, 25 Feb 2008 10:13:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[ProDevTips.com: WP Hashcash]]></title>
      <guid>http://www.phpdeveloper.org/news/9571</guid>
      <link>http://www.phpdeveloper.org/news/9571</link>
      <description><![CDATA[<p>
On the ProDevTips blog today, <i>Henrik</i> has <a href="http://www.prodevtips.com/2008/02/04/wp-hashcash/">posted about</a> an alternative to the popular Akismet plugin for the PHP blogging tool, <a href="http://www.wordpress.org">WordPress</a>, to help prevent even more comment spam from making it past - <a href="http://wordpress-plugins.feifei.us/hashcash/">WP_Hashcash</a>.
</p>
<blockquote>
WP Hashcash is an antispam plugin that eradicates comment spam on Wordpress blogs. It works because your visitors must use obfuscated javascript to submit a proof-of-work that indicates they opened your website in a web browser, not a robot.
</blockquote>
<p>
He <a href="http://www.prodevtips.com/2008/02/04/wp-hashcash/">includes the code</a> that he needed to change to get the widget part of the plugin up and working correctly. You can find out more about this plugin from <a href="http://www.prodevtips.com/2008/02/04/wp-hashcash/">its page</a> on <i>Elliot Back</i>'s blog.
</p>]]></description>
      <pubDate>Tue, 05 Feb 2008 12:09:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPRiot.com: Creating Custom Block Tags in Smarty]]></title>
      <guid>http://www.phpdeveloper.org/news/9556</guid>
      <link>http://www.phpdeveloper.org/news/9556</link>
      <description><![CDATA[<p>
On the {H{Riot.com site today, there's <a href="http://www.phpriot.com/articles/smarty-blocks">a new tutorial</a> talking about how to customize your site's Smarty templates a bit more using external plug-ins, specifically one for making those "code block" sections seen all over the web.
</p>
<blockquote>
We will first learn how block plug-ins can be used in your templates, and then learn how to create our own. Once we know how to create a block plug-in, we will cover a practical example that will show you how block plug-ins can effectively be used in your own web sites.
</blockquote>
<p>
<a href="http://www.phpriot.com/articles/smarty-blocks">The tutorial</a> assumes that you already have Smarty installed and that you're familiar enough with it to know how to work with the plug-in system right away. They include some samples of how it can be used (a default block, formatting it with HTML) and, of course, how to integrate this (PHP code and all) into your template and push your content into it.
</p>]]></description>
      <pubDate>Mon, 04 Feb 2008 07:56:00 -0600</pubDate>
    </item>
  </channel>
</rss>
