Harry Slaughter's blog

A search for "blank page" of the Drupal.org domain yields about 37,000 results.

This is probably one of the more common and frustrating problems for Drupal admins.

At BarCamp San Francisco last week, I saw a very cool remote collaboration tool called Subethaedit. Unfortunately, it's a Mac-only application. But it brought to mind the usefulness of being able to work on documents with other people remotely.

So in an attempt to enable this same sort of collaboration between myself an others, I'm setting up a PBWiki.

I just returned from BarCamp San Francisco , and I'd have to say it was a success.

This was my first BarCamp, so I had no idea what to expect. It really is as simple as it sounds. A bunch of folks show up and schedule events on the spot based on who is present and what they're interested in.

One of the great features of Drupal is its ability to run any number of sites from one base installation, a feature generally referred to as multisites . Creating a new site is just a matter of creating a settings.php file and (optionally) a database to go with your new site. That's it. More importantly, there's no need to set up complicated Apache Virtual hosts, which are a wonderful feature of Apache, but can be very tricky and tedious, especially if you're setting up a large number of subsites.

No worries, there is a solution.

IMHO, the worst part of Drupal is having to learn the API. The core developers are constantly refactoring the heart of Drupal, which is a good thing overall. But it makes it very difficult for the average developer to keep up with the API. Major version releases prior to 4.7 required a developer to make relatively few changes to his module to make it compatible with the new release. 4.7, on the other hand, requires pretty much a complete rewrite of a given 4.6 module.