[support] Modules Disabled After Updates

[Joel Willers]

If there are database/table changes, you need to run update.php in order for the database to work correctly. I can see that Drupal might check to see if the tables are correct before running malformed queries on tables that don't exist and spewing out error messages. Again, I don't know this for sure, as I always run update.php after updating anything (modules/core) in Drupal.

Joel

From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On Behalf Of Anthony
Sent: Monday, July 09, 2012 1:19 PM
To: support at drupal.org
Subject: Re: [support] Modules Disabled After Updates

What's the benefit of that Joel? 
Thanks
Tony
On Mon, Jul 9, 2012 at 11:16 AM, Joel Willers <joel.willers at sigler.com> wrote:
I think that's only if they need to be updated with /update.php

Honestly, I haven't heard of any turning off, but I always run update.php after updating.

Joel


-----Original Message-----
From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On Behalf Of Kenneth Jacker
Sent: Monday, July 09, 2012 11:42 AM
To: Drupal Support
Subject: [support] Modules Disabled After Updates

Drupal7 appears to *disable* modules after updating them.

Is that behavior a "bug" or a "feature"?

Either way, it sure is inconvenient ...
--
Prof Kenneth H Jacker       khj at cs.appstate.edu
Computer Science Dept       www.cs.appstate.edu/~khj
Appalachian State Univ
Boone, NC  28608  USA
--
[ Drupal support list | http://lists.drupal.org/ ]
--
[ Drupal support list | http://lists.drupal.org/ ]



-- 
Anthony Stefan Maciejowski