Ever any problems not updating modules where no security problems?

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
lorlarz2's picture

Is there ever any problems with NOT updating modules when none of them are associated with any security problems? I always immediately update modules where there is a security issue, but I otherwise DO NOT update modules otherwise. Could this ever be a problem????

Comments

module updating

maryannking's picture

I have tried to keep up with updates, one of the values I have with hosting at Advantage Labs is relying on them as a reference for those I need. And they usually provide me builds for my clients with the latest vetted modules with core versions. I would think that newer versions of core probably require newer versions of modules or if you're updating a module, it may have other dependencies -- Also, it is good to check the documentation and the amount of people who have downloaded the particular module.

Don't know if this is a good answer - just the way I think.

lorlarz2's picture

Your response RE: dependencies seems a noteworthy concern

But: Would Drupal.org let a person update a module for security reasons and
not force an update of modules on which it is dependent, if such updates of the
other modules were really necessary? This is a counter-question that comes to mind.

Here's why I do not rush non-critical updates:
I have had some trouble because of doing updates: One example: a new version of
webform made existing webforms not work and they had to be redone.

Perhaps for problems you haven't discovered yet

gormsby's picture

It depends, of course, but often non-security updates are addressing other problems that have been identified in a module - really, the only two reasons to update a module that I can imagine would be to a) add features or b) fix bugs. If you look at the release notes for each update, you'll see what's been deemed noteworthy to include in the update. I feel confident in saying pretty much every update includes at least one bug fix that might bite you later, even if you haven't noticed it already.

I have noticed that I am only 1 version behind

lorlarz2's picture

On the non-critical (non-security issues) modules I have not updated, I am only one minor version behind. Perhaps, I should provide the list, so you and others could perhaps spot especially important updates HIGHLY recommended (at least):

Ajax 6.x-1.14Recommended version: 6.x-1.15 (2012-Jan-21) DownloadRelease notes

Includes: Ajax, Ajax plugin - captcha, Ajax plugin - comment, Ajax plugin - webform, Ajax ui

Update available

Amazon Module 6.x-1.3Recommended version: 6.x-1.4 (2011-Nov-24) DownloadRelease notes

Includes: Amazon API, Amazon field

CKEditor - WYSIWYG HTML editor 6.x-1.10Recommended version: 6.x-1.11 (2012-Mar-30) DownloadRelease notes

Includes: CKEditor

Update available
Computed Field 6.x-1.0-beta5Recommended version: 6.x-1.0 (2012-Feb-15) DownloadRelease notes

Includes: Computed Field

Date 6.x-2.8Recommended version: 6.x-2.9 (2012-Apr-27) DownloadRelease notes

Includes: Date, Date API, Date Locale, Date Popup, Date Timezone, Date Tools

Forum Access 6.x-1.7Recommended version: 6.x-1.8 (2012-May-04) DownloadRelease notes

Includes: Forum Access

Global Redirect 6.x-1.4Recommended version: 6.x-1.5 (2012-Jun-15) DownloadRelease notes

Includes: Global Redirect

ImageCache 6.x-2.0-beta12Recommended version: 6.x-2.0-rc1 (2012-May-22) DownloadRelease notes

Includes: ImageCache

IMCE 6.x-2.2Recommended version: 6.x-2.3 (2011-Oct-20) DownloadRelease notes

Includes: IMCE

Update available
Install Profile API 6.x-2.1Recommended version: 6.x-2.2 (2012-Feb-23) DownloadRelease notes

Includes: Install Profile API

Options Element 6.x-1.4Recommended version: 6.x-1.7 (2012-Mar-17) DownloadRelease notes

Includes: Options element

Page Title 6.x-2.5Recommended version: 6.x-2.7 (2012-May-09) DownloadRelease notes

Includes: Page Title, Page Title Views SimpleTest

Pathauto 6.x-1.5Recommended version: 6.x-1.6 (2011-Oct-31) DownloadRelease notes
Also available: 6.x-2.0 (2011-Oct-31) DownloadRelease notes

Includes: Pathauto

Select (or other) 6.x-2.9Recommended version: 6.x-2.14 (2012-Jul-04) DownloadRelease notes

Includes: Select (or other)

Token 6.x-1.16Recommended version: 6.x-1.18 (2011-Nov-03) DownloadRelease notes

Includes: Token, Token actions

Webform 6.x-3.17Recommended version: 6.x-3.18 (2012-May-13) DownloadRelease notes

Includes: Webform

Any recommended ORDER when doing the updates??

lorlarz2's picture

I guess another question (and you will likely tell me to look at dependencies) is securing some advice on the order in which to do the updates. Perhaps, I answered my own question, but must one concern oneself with dependencies in figuring out the order to do updates OR is it ok not to??

P.S. I have also not updated 6.24 core to 6.26

lorlarz2's picture

I have also not updated 6.24 core to 6.26. Is this especially a noteworthy oversight on my part??

Thanks for all your help