Drupal
Drupal and open source topics.
For those of you using Domain Access, you'll recognize the problem: You need domain-specific settings.
Sure we have Domain Configuration module to expose certain settings through a single UI, but what about all kinds of other settings, especially from contributed modules? Adding exceptions in hook_domainconf() or hook_domainbatch() is cumbersome to the site maintainer, and out of scope for the Domain Access project.
What to do?
Well, you can test the Domain Settings module, which steal a few tricks from Deploy and makes it so that any form that uses system_settings_form() can be told to submit changes to a specific domain.
If anyone's really interested in the module, I may make a release. Anyone who wants to maintain it should leave a comment in the issue. UPDATE: I am also considering rolling this into the Domain Configuration module.
I see that voting for sessions is coming up fast (on 16th Feb). I actually submitted my two solo talks early, at the request of the organizers.
And, for the truly geeky, many of the features in Domain Access inspired Node Access changes in Drupal 7.
So remember to vote early and vote often.
I'll be a part of Acquia's "Playing Nicely with Others: Integrating Drupal with Third-Party Data" this Thursday, December 3, 2009 1:00 PM - 2:00 PM EST.
My portion of the presentation covers territory that I have discussed at DrupalCamp Stockholm and at DrupalCON Paris. It revolves around how to import legacy data into Drupal, with an emphasis on XML and HTML imports. We will look at strategies for handling single-use and ongoing data imports, best practices in data migration, and some shortcuts tips and modules that just might do all the hard work for you.
I am setting up API documentation for the modules that I maintain. It is a little slow-going, since API module now uses JobQueue, and I can't seem to make the site parse multiple files in one pass.
Anyway, here are the modules that will be documented here:
With any luck, these will all be up and running by the end of the week.
At long last, I have gotten around to upgrading the site. I moved from Drupal 5 to Drupal 6. And at the same time, I consolidated my old WordPress 2.8.x blog into the Drupal 6 architecture.
Two tools make this possible. One, the pretty nifty WordPress import module for Drupal. (A hat-tip, as well, to WP's nice XML export feature). The second, of course, is Domain Access, which allows multiple subdomains to run from a single Drupal installation.
With Domain Access in place, I can branch out a bit, and separate different parts of the site (and my life) to different audiences. So, for instance, the main blog is still Second Goose, where I post work-related material. On the main site, TheRickards.com, will be the best from all sites, and maybe some family stuff (mostly dog photos, probably). For fun, there is \m/etal.therickards.com where I will talk about heavy metal and albums I like. And I set up API.therickards.com to host API documentation for various modules that I maintain.
There may be a little dust flying around for a few days while things get settled. Hopefully there aren't too many broken links on the site. I also have to get ImageCache and its family of modules running later.
