By Phil Ewert on

Hi all !

To update the Drupal-Core (e.g. 5.7-> 5.10 ) it is prescribed (in the handbooks and so) to disable all modules. Now, I have a lot of them and it would be some hours work to note all of the enabled down, disable them and afterwards enable them again. Question : What is the risk, if I don't disable them.

Technically : What can go wrong ?

My (probably shortfalling) understanding : By disabling modules you only change a status bit in a table of the DB (apart from that you have to disable them in cascades of depending modules). What does running the Update.php change technically on contrib modules?

Here some prior sources, I found, not shading light on my technical questions.

http://drupal.org/node/102570
http://drupal.org/node/189954
http://drupal.org/node/300331

Thanx for your awnsers in advance,

Phil

Comments

AccessiveApps’s picture

AccessiveApps commented

Make a snapshot of your db and update ... the update.php is calling e.G. http://api.drupal.org/api/function/hook_update_N/6 to reflect all db scheme changes in your database.

After more then 3 years of Drupal I never had a problem that broke my site. BUT make a db snapshot ;)

--patrick

xmacinfo’s picture

xmacinfo
he/him
Primary language French
Location Canada
commented

When doing dot release updates, you don't need to disable your modules. Disabling modules is recommended only if you do a major upgrade (e.g. 5.7 to 6.4).

Like said in the comment before, do a database backup as the fist and most important step.

From time to time, though, some modules will require their own update when upgrading your Drupal installation to a new dot release. This may happen when an API is modified and developers using the API are asked to issue an update. So it's always a good idea to check out if any modules have been issued an update.

/*_*/
http://www.xmacinfo.com