Error message
Deprecated function: Methods with the same name as their class will not be constructors in a future version of PHP; GeSHi has a deprecated constructor in require_once() (line 915 of /var/www/davidherron.com/sites/all/modules/libraries/libraries.module).
Drupal tips, tricks, tutorials
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.
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.
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.
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.
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.
Submitted by Anonymous (not verified) on Wed, 2010-04-21 16:50
Submitted by Anonymous (not verified) on Thu, 2010-01-14 11:57
Pages