We noticed that drush automatically respects the settings of the update_advanced-module. I assume this works because drush uses the update-module for the updates, and update_advanced integrates with it?

So if I have set "views" to update "never" at http://example.com/admin/reports/updates/settings , "drush up views", it will show views as "Unable to check status " and respond "No code updates available." even if there are updates. Exactly what we need to exclude patched modules from being overwritten.

In any case, it works fantastic, but surprisingly, this feature is not documented anywhere (!), at least not in drush or update_advanced's issue queues (drush & update_advanced).

This combination has been very useful, we have been using it in our workflow for about a year now. It's the reason we even use update_advanced, apart from documentation.

Sorry for screaming for attention by setting this to "major", but I believe if this fact was properly documented (maybe even on the frontpage of the module), this module might have a lot more (happy) users.

Comments

moshe weitzman’s picture

moshe weitzman CreditAttribution: moshe weitzman commented

FYI drush HEAD has a similar feature where you can lock any project so it does not get updated.Perhaps we didn't beed to do that. We did not know about this module.

Robin van Emden’s picture

Robin van Emden CreditAttribution: Robin van Emden commented

I second the importance of this feature, our organisation depends heavily on it. Wasn't aware it was an undocumented feature though. I think this most certainly warrants the "major" priority.

Leeteq’s picture

Leeteq CreditAttribution: Leeteq commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
firfin’s picture

firfin CreditAttribution: firfin commented

Yes, still an issue.
No mention of this incredible tidbit of information anywhere.
Neither on homepage nor in readme.

AohRveTPV’s picture

AohRveTPV CreditAttribution: AohRveTPV commented
Status: Needs review » Active

"Needs review" status should have a patch, per https://www.drupal.org/node/156119.

AohRveTPV’s picture

AohRveTPV CreditAttribution: AohRveTPV commented

#2431483: Add Drush commands adds Drush commands for configuring this module. If interested, please review/test.

I do not think the commands would be redundant with drush up --lock, etc.:
1. Drush update locks seem to be limited to affecting update checking via Drush and not the Update Manager module.
2. --lock ignores updates for a project until unlocked. It is equivalent to the "Warn if out of date: Never" setting in this module. There is no way though to ignore only a specific recommended release. For example, you are running 7.x-1.0, and would like to ignore 7.x-1.1 but would still like to be notified if a 7.x-1.2 is released.