Proficient in one or more of PHP, SQL, CSS and HTML. Can fix problems from the mysql command line. Familiar with the Drupal API.

hook_settings pain


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.

The Weak Link in Drupal Scalability (99.9% of you can ignore this article)


Drupal is as scalable as the applications it relies on. While there's nothing preventing Drupal itself from being scaled across any number of web servers, scalability of open-source databases such as MySQL and PostgreSQL is an ongoing issue. While these databases do support replication, that's not always enough. For a very small percentage of websites, daily user visits are counted not in hundreds or thousands but in hundreds of thousands.

user sequence gotcha

Wasted a lot of time due to this doozy in the drupal code (user.module): <?php ... $array['uid'] = db_next_id('{users}_uid'); ... ?>

So let's say you want to share a users DB between two drupal sites, A and B.

For site A, you configure your settings.php normally. This will be your master DB.

In site B, you point user related tables to site A's database:

redirecting all possible hostnames to one using mod_rewrite


SEO experts claim that having multiple hostnames point to the same site will result in lower rankings for that site. It's common to see sites accept both "" and "".

I have no idea if this is true, but it makes a bit of sense, so why take the chance.

I want to direct everyone to "" regardless of what they type in, with one exception. I want to allow for a hostname for my own devious purposes. This is what I'd put in the mod_rewrite section of my .htaccess or httpd.conf file:

module for managing multi-dimensional node objects


I've got a problem I'm trying to solve.

I want to a module to manage inter-related data sets.

Imagine a chain of retail stores that carry different products and have a multiple ongoing sales. We'll call the module "storemanager".

Each store will have its own properties along with various active sales and its own unique products. Each sale will have properties plus a list of products that make up the sale. One or more stores may have the same sale. Finally, products will have properties, and they may be present at one or more stores and in one or more sales.

Syndicate content