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.
I listen to a couple podcasts by Cliff Ravenscraft (Podcast Answerman and Social Media Serenity) and really value the information he gives. But something he’s said a few times recently has been bugging me but a couple brain cells just clicked and I think I get it now. One of his recommendations is to look through your followers on Twitter and remove those that you don’t like (e.g. if they’re spammers). Yes, Twitter is full of spammers but that doesn’t mean you have to play the spammer game.
Just listened to the latest episode of The Doctor Who Podcast where they reviewed The Lodger. They described that episode as being a ho-hum filler which doesn't have much in it in terms of clues for the season-ending grand finale. And indeed it sure looks like a ho-hum filler. It's a normal middle-of-the-season story that has a lot of interesting bits to it, is well told, but is not the ground shaking extravaganza.