Music For Life is an event organized by Studio Brussel to support Red Cross initiatives. It took place for the first time in 2006 to aid land mine victims. The main event is 3 radio dj's locking themselves up in a glass house and bring non-stop radio for 7 days, playing requests for a donated amount by the listeners. They only get to drink fruit and vegetable juice and they don't get anything else to eat. The Flemish Government sponsored 100.000 euro and the Federal Government doubled the end result, for a total of 2,4 million euro!

The second edition, which ended on the 24th of December, was all about water:

• providing structural and long-term solutions to supply pure and drinkable water to the most vulnerable of the developing countries like Namibia, Mozambique, Nepal, Rwanda...
• supplying pure and drinkable water to victims of disasters, like those in Sudan and Ethiopia

This year the Flemish Government sponsored 150.000 euro and the Federal Government added 1 million euro, for a grand total of 3.353.568 euro!

On the Drupal-powered portal of Music For Life movies were posted of what was going on the in the glass house, there were several live video streams and users could send in pictures, video and audio of their own actions for this event.

I'm looking forward to next year's edition!

Continue reading »

Working at the VRT I've had the pleasure of upgrading Toyinima from Drupal 4.6, 16plus.be from Drupal 4.7 and Studio Brussel from 5.1 to the newest Drupal 5.3. These were core-altered installations with a lot of custom and contribute-altered modules. I started of by dividing the non-core modules between those still in their original state to a "contrib" directory and those that were either completely custom or altered in a "custom" directory, to get the following tree structure:

This helps you identify what needs to happen and will also save a lot of work for future upgrades. I then started from a clean Drupal 5.3 installation, download the newest version of the modules in /contrib and then started a process of 1) moving the core changes to non-core modules and themes and 2) updating the /custom modules.

I must admit updating the custom modules went a lot faster than I imagined. Drupal 4.6 took by far the longest time with upgrading the forms to the FormAPI as well as updating the theme. What took the most time for all three sites was identifying the alterations done to core, what they were doing and how this could be moved to the modules and templates. The developers did a fine job documenting their changes to core, which made things a lot easier. Some of these changes were patches offered in the d.o issue queue (not necessarily by the module maintainers) as quick bug/security fixes, like this issue for the event module.

Two things to remember:

Upgrading Drupal is not a scary task. People refrain from upgrading because they fear it might fail and break their site. Keep your head cool and make an index of changes that need to happen: divide your modules in altered and non-altered versions, identify any changes made to core and take it one step at a time. There's plenty of good documentation to help you and people in the forum and on #drupal-support are waiting to help you on your way.

Once again, please don't alter core, don't even suggest altering core as a quick fix. The time you win by "fixing" the issue in this manner is lost twice when upgrading later.

Continue reading »