Have an old Drupal 6 site that has a lot of available updates for modules, core and theme.

When a module has several updates available from the currently installed one to the latest, I understand it's safer to apply them in order. Can I skip this and just install the latest version of the module? Is there a way to know when it's safe, and when not? Visiting updating notes tells about bug fixed, but no info about this. Is there a way to know if the update will make changes to database, so if I have a pre-production and production enviroment, can plan accordingly?

Also for core Drupal updates, I think that in that case applying every update in order is mandatory. Am I right?

I've checked official Drupal information abaout updates, but doesn't state anything about it (it says that you can update multiple modules at the same time, but beware of dependencies between them).

2 Answers 2


Installing the latest version straight off should be fine in most cases.**

If the module updates only contain minor code changes then there's almost certainly nothing to worry about.

If the module updates contain more major changes such as alterations to the database schema then the module maintainer should be using the hook_update_N() function in a "module_name.install" file which will allow Drupal to determine which updates fall between your currently installed version and the latest version, and apply the necessary modifications in sequence, meaning no breakage should occur. Drupal core is no different to any other module in this respect, so you should also be able to update to the latest core version without any problem.

**If the module has seen a major version increase, for example, you have 6.x-1.7 installed and the latest version is 6.x-3.2, then you should check the module's project page and documentation for any compatibility notes or special instructions for updating. In some cases the versions may not be compatible and would need to be manually migrated, or some dependency may have changed, which the module maintainer should inform you about somewhere.

The only other problem I can think of is the unlikely situation where an API change has occurred in Drupal core at some point and one of your modules was abandoned and never updated to take account of the API change. In that case, you may need to find a patch in the module's issue queue, disable the module, or find an alternative module.

Also, this may be stating the obvious, but if your site is running on Drupal 6, you won't be able to install any module updates with version numbers beginning 7.x- because those are for Drupal 7 and won't be backwards compatible. You'll have to stick to the latest 6.x- version.

Having said all that, you should always carry out a test run of the update process in a testing environment before you go anywhere near the production server. Make sure to clone the live database and all the Drupal files from your production server to your test environment so that you can safely determine exactly what effects the updates will have.

  • Thanks for such a detailed answer. I'm right now doing several tests about updating, following your advices. Will accept upon completing them and analyzing the result. Jun 15, 2015 at 10:19
  • Accepted as the most detailed answer. Tested several times, and I was able to update all modules, themes and core to 6.36 in a single run for a site not updated since 2011. Worth noting the addition of "Libraries" module, that makes modules like PHPMail require now to download and put aditional file on sites/all/libraries folder. Jul 3, 2015 at 7:18

In my opinion it will not hamper your site when you update a module or core skipping a few upgrades. Though it is necessary to test out the changes in a test environment after installing upgrades.

You can follow the instruction here https://www.drupal.org/node/250790

  • Thanks for the quick answer, Malabya! I'm going to wait for further opinions, if everyone agrees, I'll mark your answer right. Jun 8, 2015 at 12:07
  • My experience says your answer is usually untrue. Most of the time it worked well for me. Of course testing is good and encouraged. In private pet projects I rarely do it.
    – Mołot
    Jun 8, 2015 at 14:15
  • Umm.. I did a bad typo out there.. I meant it will "not" hamper the site but a thorough test is required. Jun 11, 2015 at 11:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.