paul bennett

Archive for the ‘PHP’ Category

Drupal’s module installation system makes it very easy to extend and customise Drupal sites and to disable and re-enable modules quickly and non-destructively. However, the default way Drupal’s treats modules can get in the way during development.

When building your own modules, it’s common for database table structure to change as project needs become clearer, or even for modules to be built in a “front to back” fashion – where the admin screens and the UI interaction skeleton is built before the underlying processing and data storage code is developed (or finalised).

If this is the case, you may find yourself building an install file late in module development and then wondering why Drupal seems to dutifully ignore it.

Despite being counter-intuitive, this behaviour has some clear benefits. Previously installed modules may have attached database tables, and these tables may still hold valid application data. Drupal’s behaviour ensures that these tables aren’t destroyed when the module is disabled. The module can then be re-enabled later without any data destruction.

To get a module to run an install file, or to re-install successfully, you need to do more than just disable and re-enable the module on the module list screen (/admin/build/modules). This is beacuse¬† Drupal keeps a record of previously installed modules and won’t reinstall them if they are merely disabled and re-enabled.

The trick to getting your new / updated install file to run is to remove the modules entry from the system database tables. If your module has already created one or more tables, and you want the table structure to be altered or rebuilt, you may also need to remove these tables before re-enabling the module.

Once you’ve disabled your module, removed the related entry from the system table and removed any module-related tables, you can re-enable the module and your install file will be run correctly.


It has somewhat of a steep learning curve, but Drupal is amazing for allowing you to build flexible, complex websites with lots of functionality in very little time.

For a site I’m working on, we had several custom content types coming through the default node template (node.tpl.php) in our customised theme.

This was fine and dandy for quick development, but then the time came to customise the node page for each content type.

First things first, you need a custom node template. Save the node.tpl.php file as node-[your node name].tpl.php and you’ve created a custom node template. (This means if your node type is ‘audio’, you’d save the file as node-audio.tpl.php)

Now we need to customise the template to suit our needs.

If you dive into a standard node template you’ll see something (unhelpful) like this where the content goes:

<div class=”content”>

Um, OK. So how do you get at the functions which compile the content before it gets to this stage? Well, you probably can, but the easier way is to avoid this step and just access the default $node object which drupal gives you access to with each ‘page’.

To find out what’s hiding inside the $node object, simply do something like this:


(Yes, I like print_r())

The resulting cacophony in your page source will show you all the node attributes and properties you have access to. Chances are you’ll be able to access these directly to create the customised node template you need.

One of my most used bookmarks is this wee gem:

In Firefox, it set up this bookmark with the keyword ‘php’*.

This lets me type ‘php function name‘ into the address bar and takes me straight to the manual page for that function.
For example, for the date() function, I can just type

php date

and go straight to the date() manual page (

Simple and so, so handy

*You need to use the bookmark manager to do this


Looking for good PHP books? I recommend the following:

Being frustrated with the tinymce plugin for Expression Engine, I decided to create a rich text editor plugin for Expression Engine using the YUI library simple editor.

Due to a magic combination of:

  1. the awesomeness of the YUI library
  2. the thoroughness of the YUI documentation
  3. the simplicity of creating extensions for Expression Engine

it was surprisingly straightforward.

If you’re using Expression Engine and are either sick of fighting with tinymce or aren’t using a rich text editor, you can download it from

Consider the following:

// do some stuff

$settings = array('server' => 'locahost', 'user' => 'paul', 'password' => 'secret', 'database' => 'stuff');

$linkId = mysql_connect(/* db settings go here */);

Seems perfectly reasonable. myscript pulls in the settings, which then pull in the database connection functions.

On Solaris, however, the first file is included fine, but the second fails. Silently.
As you can imagine, this leads to much unneeded debugging. Not to self:¬† you can’t debug something well if it isn’t actually broken.

A search at doesn’t turn up anything, so it may be our server setup. If anyone is also using Solaris 10 and Containers and has this bug, please let me know.
Otherwise, you have been warned.

I used to think this was hard. Turns out it’s pretty easy.

PHP and Cron

Posted on: May 30, 2007

If you’re using the cron process to automate parts of your site / application, ensure you aren’t relying on superglobal variables like $_SERVER.

Apache provides information for the $_SERVER array (‘SERVER_NAME‘, ‘DOCUMENT_ROOT‘ etc), and as cron doesn’t run underApache, it has no access to information inside the $_SERVER array.