DNotes LLC

DNotes LLC

Drupal development, hosting, and consulting

Planet Drupal

Maintaining an in-house Drupal install profile (aka distribution)

A few years back, when Drupal 6 was gearing up for showtime, one of the major working points was making the install profile system easier to navigate for developers. A Drupal install profile, also known as a distribution, allows you to specify an initial setup for Drupal, including both core and contributed modules, and setting up configurations for them.

Updating module versions in an install profile

Maintaining install profiles I am constantly having to maintain drush make files of contributed modules. Drupal.org used to display which modules were out of date on the dev release node, which made it easy, but that's gone now. I asked another distribution maintainer at Drupalcon a few weeks ago, and he just used the update status list. That works, but it's annoying to wait for the updates locally, sometimes having to run cron, and a little tedious to go through all the list of modules.

Views query alter methods

Views is a fantastic module that allows you to build complex database queries through configuration. However, I've found that a weird variation of the 80/20 rule applies to views: 80% of the time, the configuration will get you 100% of what you want, but 20% of the time, it will only get you 80% of what you want. That's where the views hooks are handy, especially hook_views_query_alter. I've used this many times - adding a where clause, modifying a field, etc.

Quick and dirty migration to new Aegir platform

I've been trying out the managed Aegir mini offering by Omega8.cc, and been quite happy with it. A few days ago I got a message that I needed to migrate them over to another platform because they weren't on a Pressflow-based Drupal 6 platform. These are sites that I haven't touched for a long time - apparently, in fact, since before I started using Pressflow. So then: how to migrate the sites without spending a lot of time on them? I decided to just move all the code into each site's folder and then migrate. Here's how to do it:

Quick add new ticket form block in OpenAtrium case tracker

One of the things that annoys me about all ticket management systems is the amount of time that it takes to add a new ticket. Click the project; click for a new ticket; wait for the page to load; enter a title; select a priority; assign to a user; select other options; enter a longer description; click "Save"; wait for the page to load; rinse and repeat. That's a lot of overhead just for adding a ticket! I've tried unfuddle, basecamp, jira, and openatrium, all with the same complaint.

Pages

Subscribe to RSS - Planet Drupal