EB now upgraded - from Drupal 5.7 to 5.16 -- scary...

I have to give a big hand to all the module developers that make upgrading smooth. I was very hesitant to upgrade my Drupal install and the contributed  modules since it has been 14 months since my last big upgrade.

I thought I would just share with you some details...

1 hour before this blog post I was running on Drupal 5.7 with 13 outdated contributed modules.

• captcha
• cck
• comment_notify (patch required)
• demo
• devel
• forward
• google_analytics
• imagefield
• pathauto
• tagadelic
• taxonomy_intro
• tinymce
• update_status

That said, I hesitated as I was afaid my custom module, elvisblogs, that overrides other contributed modules, would break. To my surprise, no breakage has been found yet.

There was one module I could not update, since it has been deprecated  - the monthly archive module. I use this module in the archive block in the top right section. On the module page a view is suggested now. Not everyone uses views (rare these days but true). For EB, I modified the "monthly archive"  module - so maybe I should give back the code...

Back to updating... I will say, when running update.php no query problems were reported, that is a good sign :)

The only thing out of the norm, of updating, was patching the comment.module - which is a core module. Other than that, no real work was involved. The real work was backing up everything before doing the updates. ;)

Thanks to the above module maintainers for staying on the Drupal path - writing good modules according to Drupal standards.