June 2010
Integrating the Features Server into OpenAtrium
grayside — Thu, 06/03/2010 - 08:32
Working on integrating the Features Server feature into OpenAtrium. My intention is to set it up as another Casetracker Project type.
OpenAtrium provides a solid case tracker and documentation system, and is a natural fit for the infrastructure of a Drupal.Org-style project ecosphere. Integrating them will allow me to post Features I’ve created to a place where I might actually have a means to get feedback on my work, let alone provide support.
Automatic Nodetitles is Usually Overkill
grayside — Wed, 06/09/2010 - 15:42
I’m not a huge fan of the Automatic Nodetitles module. It’s got a lot of user interface overhead, and yet I’ve never given a non-programmer access to that administration page. On top of that, someone gets a headache from it on one of the forum sites I frequent every few weeks.
For those with the programming chops to avoid it, why keep the overhead of an entire project, when a custom module snippet will probably be more than enough?
Drush with Bash Aliases
grayside — Wed, 06/09/2010 - 22:18
I’ve been looking for some decent ways of managing the use of modules hosted in random Features Servers. Particularly, how do I use Drush as seamlessly with a Features Server as it works with Drupal.Org?
It turns out that Drush has a lot of special options buried in the pm-download (dl) command, the very Drush maneuver most helpful for my goal. Naturally, these options can be included in a Bash Alias for Drush.
Optional Spaces Integration for a View
grayside — Tue, 06/15/2010 - 13:05
If you want to make an exported [node-based] View smoothly integrate with Spaces, you can use the following code to modify the View structure with the “Content in current space” filter. This filter does nothing if the View is not itself in a Space, otherwise it restricts all results to content in the same space. Add any conditions you want to control whether the Spaces integration is applied.
Firefox's Custom Keywords and Drupal
grayside — Tue, 06/15/2010 - 13:50
If you’ve delved into some of the enhanced bookmarking magic in Firefox, you know that entering the world of the Organize Bookmarks tool provides some additional options in how you save your bookmarks.
Custom Keywords are really neat. I use them for Drupal reference all the time. It’s my preferred method for bouncing around CVS, the API, and issue queues. Typing “d6 hook_nodeapi” to double check the ops is very nice. Typing “dcm og” to start researching how og access control works save a page load.
Attached is a drupal-bookmarks.html file that will get you a leg up on the boring process of creating these bookmarks.
It includes Drupal Project, Drupal Project Issues, Drupal Project Usage, Drupal CVS Modules, Drupal CVS Core, Drupal Site search, Drupal 6 API lookup, and Drupal 7 API lookup.
(You can create something similar in Chrome, but it’s not done through bookmarks. Setting up Custom Search Engines is very similar, and I don’t see an easy mechanism for exportables.)
Modifying Contexts the Old-Fashioned Way
grayside — Mon, 06/21/2010 - 15:05
There are two ways to change contexts. The new awesomeness is to use Features or other exportable techniques to create a new version of your modified contexts, and push the old ones out of the way.
However, when I avoid hacking [atrium] core, I prefer the old way—today that’s alter hooks.
