Drupal tips, tricks, tutorials

Using "drush make" to maintain the source tree for a Drupal site, and avoid killing kittens

To avoid killing kittens through hacking Drupal core I've been maintaining a source tree using Mercurial (see: How to use Mercurial to hack Drupal Core without killing kittens). But, I had an inspired idea recently to see how well "drush make" could take care of the job and maybe stop using a private source tree. One of the key required features would be to maintain a set of local patches. I'm pleased to report some positive success and it looks like a useful method for a D6 to D7 upgrade.

Blocking an undesired item while using the Amazon Store module for Drupal

The other day I was contacted by a lawyer about an improper use of their trademark. Unfortunately the improper use stemmed from a product listing controlled by the "Amazon Store" module, and is in data retrieved from amazon.com using their affiliate product web services API. The "Amazon Store" module implements something like the "aStore" feature supported by amazon.com, but hosted on a Drupal site. Because all the data comes direct from amazon.com there is little control over how it is displayed.

Maybe the Domain Access module causes more trouble than it's worth?

I've been trying out the Domain Access module and made a couple blog posts describing the learning (see: Configuring Drupal blocks when using the Domain Access module and Looking at (and a debugging tip) the Domain module for Drupal). In a comment, David Hansen Lange made an observation that's been in the back of my mind.

Configuring Drupal blocks when using the Domain Access module

Following on from my blog post the other day, Looking at (and a debugging tip) the Domain module for Drupal, I want to look at one of the gaps in the Domain Access module. Out of the box it does not modify the blocks configuration pages, meaning that out of the box all configured blocks show up for all domains. This is unlikely to be what you want, instead what's likely is to have different blocks for different domains.

Looking at (and a debugging tip) the Domain module for Drupal

This week I decided to try out the Domain module for Drupal. The immediate goal was to support multiple domains and what looks like multiple websites out of one Drupal instance. I'm thinking there might be an advantage where the content across related websites could be more easily cross-referenced between the sites. Plus I'm expecting a maintenance gain from having one Drupal instance rather than several. Plus I'm working with an organization that could want to support multiple websites for its committees.

Kicking the tires of Drupal's Features module

As noted in a previous blog entry, Quick look at the Package Builder module for Drupal, and prepackaged functionality, I'm associated with a gang of people thinking about creating a packaged Drupal distribution. In the previous blog entry I looked at Package Builder, and in this one I'm looking at the Features module.

Quick look at the Package Builder module for Drupal, and prepackaged functionality

The Features module has been getting a lot of attention and a couple projects are using it to neatly package up clumps of functionality to share with each other. This idea of packaging a clump of preconfigured functionality is very attractive and I think there is great potential for a marketplace of these things to form. Since DrupalCon SF I've been involved with launching a project where we want to use preconfigured packaged functionality to share with a specific community of people. Hence I'm evaluating the ways to do this packaging.

Participating in the global web of communication and comments

I'm at DrupalCon and am having a great time. This note is based on a talk yesterday PubSubHubbub to the rescue-- Real-time feeds and the future of social networks which gave me hope for a solution to a problem I think is vexing us all.

Pages