With the release of Mac OS X 10.5 Leopard last fall, Apple (finally) included a modern version of PHP (currently version 5.2.6 as of this writing). [...] However, the default install of PHP that Apple included didn't include all of the available PHP extensions. Most notable is the IMAP extension, which is used in SugarCRM for the Campaigns and Emails modules. However you can build this extension and have it loaded dynamically, without affecting the rest of the default PHP install.

He shows where to get the packages and libraries you'll need to get the support working. The method involves building a shared module and including it to be loaded in your php.ini. This way it doesn't disrupt anything the current build has and you don't have to recompile everything over again.

What if you [also] want to support collaborative editing of content, community forums, and other capabilities that could help increase traffic to your site, but are usually only found in content management systems (CMSs)? Is it possible to combine the best of both worlds - shopping carts and CMSs? Fortunately, the answer is yes, if you choose a world-class CMS such as Drupal as a foundation for your site.

They walk you through how to get the module installed, how to configure it to match with your site's layout and flow and how to hook the purchase process into PayPal to make purchasing a few simple user clicks away.

More and more users are finding it difficult to load models within Zend Framework modules. This is strange, considering that modularity is an important design principle and its goal is to design systems that are easier to extend, understand, design and manage.

He brings in quotes and examples from different developers' blogs talking about their use and brings it up to the present day with an example of using a Zend_Module_Front controller with a Zend_Module_Action in a simple example of a module-specifc method for using a model.

suPHP is a tool for executing PHP scripts with the permissions of their owners. It consists of an Apache module (mod_suphp) and a setuid root binary (suphp) that is called by the Apache module to change the uid of the process executing the PHP interpreter.

suPHP runs as an Apache module and works with the local server's permission system to restrict script access to whatever the user's allowances are. He links to this tutorial for more information on setting it up.

In my quest to do some alterations on ZF error handling (in particular, render the view if the action or controller is not found, makes it real easy for my designer to prototype) I had the desire to be able to allow modules to have their own ErrorControllers. Unfortunately, the Zend_Controller_Plugin_ErrorHandler() default does not allow for this and I didn't really want to extend that class (I planned on handling the rendering in the ErrorControllers) so I wrote up a quick plugin.

His plugin (code included in the post) hooks into the routeShutdown part of the routing process and overrides the default error handler for the module to pass the request off to his custom one.

Lots of programmers like PHP for its ability to code and develop web applications fast. Code-debugging is a lot easier than with PERL or C. However, there is one thing a lot of developers are puzzled about, "How to run PHP Scripts with crontab?"

He explains how cron can be used effectively to replace including a backend script into another file (bad practice) and how to get started with PHP and cron. He includes how to find if you're using a CGI or Apache version of PHP and how to locate the binary. He takes this knowledge and shows how to apply it and put a sample script into the cron file. You can check out sites like this or this for more information on cron itself.

You can encapsulate routes into modules by splitting the routes into different files and extending the Zend_Controller_Router_Rewrite class. But, what if you want to use the Redirector helper to set a URL based on a registered route?

His method creates the routing instance and overwrites the default getRoute method with a custom one in the extending class.

Symfony is one of the few PHP frameworks that gives you basic tools for starting to write tests. [...] Symfony also provides an extension of this class called sfTestBrowser, designed especially for functional tests, which has all the abilities of the sfBrowser object plus some smart assert methods.

He uses this sfTestBrowser object to run an example test on a same get() call's response. It should match the regular expression of "/This is a temporary page/" but doesn't so it fails. Writing up tests like this for new parts of your application first would be considered test-driven development and the Symfony framework makes that simple.

Whether you're an enterprise developer working in a large shop or setting up a blog for yourself, you've almost certainly been tasked with keeping your development code in sync with some type of stable release. Whether a project is big or small, you still need to ensure that the core code you work with remains consistent.

The tutorial walks you through the setup of a basic AIR application, how to pull the configuration XML into it and parsing it to use in the interface. The next step is the sync, grabbing your config and pushing it out to other multiple configs across your sites (via a REST service).

First of all I decided to add an Entries Model and Authors Model to the mix, primarily to get ready for when we can add new entries to our blog. This leads to where we can create new Entries; we add an Administration Module to the application with it's own distinct Layout.

He starts by making the database schema, an entries and authors table, before starting in on the models. They're made based off of the Zend_Db component's structure and they let the application interact with the data in the tables easily. His code for the modules is included as well as the controller and view for the admin module.