Saturday, December 06, 2008
Unfortunately when something strange happens many users think that it's a problem with something thy did and they just don't understand this big complex piece of software and they never will get the hang of it and blah blah blah. And of course no user of a site should be expected to go to a module's drupal.org page and look at the open issues to see if anyone else is having the problem. My take-home from this is to be very wary of software module updates, and to not just trust something because it is an official release of a module.
The classic double-edged sword of open source software development, a developer might be working on a bit of code to suit his own needs, and just not do enough diligent checks that he hasn't broken some other feature unintentionally. Drupal is finally getting into active automated testing, but this won't help you if you are using a module that isn't part of the mainstream set of actively-developed modules. Maybe all this is telling me to take up the mantle of contributing in more active and complete ways to keep the modules I want to use alive.
The slow hard but rewarding lesson of Open Source.