Raised Eyebrow Blog

Discovered a very upsetting scenario today while building out a Drupal 6 site. If you have the Update module enabled and drupal.org goes down your module admin page at www.example.com/admin/build/modules stops responding. Why? I think it’s because somewhere in the Update module is a call to updates.drupal.org.

The quick and dirty solution is to temporarily disable the module via the system table in your database.

How do I do that?

• Using phpMyAdmin or some other GUI tool or via the command link
1. View the system table contents
2. Find the row where filename is modules/update/update.module
3. Edit the row and set it’s status field to 0
4. Refresh your modules page
• Via SQL Query/command line

  UPDATE `system` SET `status` = 0 WHERE `filename` = 'modules/update/update.module'

I’m going to submit an issue about this and look into a possible solution. I was halted in my work for over an hour today because of this.
Disclaimer: I am not responsible for those of you who do not backup before making any changes to your database.

Tags: Drupal, modules, update status

This entry was written by Colin Calnan on Thursday, March 26th, 2009 at 2:43 pm, is filed under Code and Coding, Content Management Systems, Drupal, Geekery, and is tagged as Drupal, modules, update status. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.