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@cs.appstate.edu Computer Science Dept www.cs.appstate.edu/~khj Appalachian State Univ Boone, NC 28608 USA
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@drupal.org [mailto:support-bounces@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@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/ ]
What's the benefit of that Joel? Thanks Tony On Mon, Jul 9, 2012 at 11:16 AM, Joel Willers <joel.willers@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@drupal.org [mailto:support-bounces@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@cs.appstate.edu Computer Science Dept www.cs.appstate.edu/~khj<http://www.cs.appstate.edu/%7Ekhj> Appalachian State Univ Boone, NC 28608 USA -- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
-- *Anthony Stefan Maciejowski*
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@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Anthony Sent: Monday, July 09, 2012 1:19 PM To: support@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@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@drupal.org [mailto:support-bounces@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@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
On Mon, Jul 9, 2012 at 2:18 PM, Anthony <tony@tony-mac.com> wrote:
What's the benefit of that Joel?
It's an absolute must when updating modules or Drupal core to execute update.php. Not doing so will soon bring your system to a halt. See drupal.org/documentation, drupal.org/upgrade, drupal.org/node/635460 for more info. -- Earnie -- https://sites.google.com/site/earnieboyd
Junk junk junk Sent from my iPhone On Jul 9, 2012, at 2:28 PM, Earnie Boyd <earnie@users.sourceforge.net> wrote:
On Mon, Jul 9, 2012 at 2:18 PM, Anthony <tony@tony-mac.com> wrote:
What's the benefit of that Joel?
It's an absolute must when updating modules or Drupal core to execute update.php. Not doing so will soon bring your system to a halt. See drupal.org/documentation, drupal.org/upgrade, drupal.org/node/635460 for more info.
-- Earnie -- https://sites.google.com/site/earnieboyd -- [ Drupal support list | http://lists.drupal.org/ ]
If it's disabling them then you got a bad module in there or something weird going on in the database. I have never had Drupal 7 disable any modules after updating them. Jamie Holly http://www.intoxination.net http://www.hollyit.net On 7/9/2012 12:41 PM, Kenneth Jacker wrote:
Drupal7 appears to *disable* modules after updating them.
Is that behavior a "bug" or a "feature"?
Either way, it sure is inconvenient ...
The profile module in D7 is hidden but not disabled. You have to modify the profile.info file to remove the hidden attribute for it to show in the modules list. Earnie On Mon, Jul 9, 2012 at 3:06 PM, Jamie Holly <hovercrafter@earthlink.net> wrote:
If it's disabling them then you got a bad module in there or something weird going on in the database. I have never had Drupal 7 disable any modules after updating them.
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 7/9/2012 12:41 PM, Kenneth Jacker wrote:
Drupal7 appears to *disable* modules after updating them.
Is that behavior a "bug" or a "feature"?
Either way, it sure is inconvenient ...
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Earnie -- https://sites.google.com/site/earnieboyd
participants (6)
-
Anthony -
Earnie Boyd -
Jamie Holly -
Joel Willers -
Kenneth Jacker -
Michael Tinney