As reported by nancyw over at http://drupal.org/node/153741#comment-262994 -- some people don't want to be bothered all the time for updates, since not every contrib maintainer is super careful and sometimes new releases just break stuff. However, instead of not running update_status at all, these people should run it in a mode where it only flags stuff as red and causes the status report to ping you if there are security updates. Should be easy to add a set of radios on the settings page for what severity to consider an runtime requirement error. Something like:
Warning severity level:
Select what kinds of new releases should be marked as a warning so that the [status report] and the [modules] page will indicate that new updates are required for your site to be up to date.
Once this is in core and everyone's running it, we're going to want a way to quiet it down like this, for sites that only want to be bothered for security updates. That said, there should be no way to disable the error for security releases. D6 should *force* the admin to see it when a security update is available.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | update_status_error_threshold.patch.txt | 7.73 KB | dww |
| #9 | update_status_settings_tab_help.patch.txt | 3.72 KB | dww |
| #7 | update_status_only_security.patch_2.txt | 4.95 KB | dww |
| #5 | update_status_only_security.patch_1.txt | 5.69 KB | dww |
| #4 | update_status_only_security_report.png | 41.75 KB | dww |
Comments
Comment #1
killes@www.drop.org commentedYeah, makes sense to me. I remember bein super annoyed when I got told to update some module twice a week.
Comment #2
dwwComment #3
dwwscreenie of the new settings tab
Comment #4
dwwscreenie of the resulting report. note that there are 2 modules that would otherwise be marked as updates, a dev snapshot (taxonomy_context) and an official release (views). i like the fact that it still tells you an update is available (if you read closely), it's just not marked as red, and therefore, the status report and modules pages are quite. i'm quite pleased with this. ;) of course, if you install an old module that has a security release available (audio 5.x-0.1 is my favorite test case for this), it'll get flagged red no matter what...
Comment #5
dwwI was trying to be fancy and not save the setting if it didn't match the default. Unfortunately, that actually breaks things in a few cases. ;) So, here's a patch that's trying to be less smart and therefore works correctly.
Comment #6
dwwCommitted to HEAD as revision 1.63 of update_status.module.
Comment #7
dwwActually, "Warning severity level" is confusing and sort of a misnomer. "Warning threshold" is better. A few other tweaks to the wording.
Comment #8
dwwCommitted that one, but I'm rolling another for yet more cleanup...
Comment #9
dwwComment #10
dwwCommitted a slightly modified version to HEAD. Thanks, webchick!
Comment #11
dwwDrat, the more I think about this setting, the less I like that I called it a "Warning" threshold, when it's really an "Error" threshold.
Comment #12
dwwwebchick and add1sun liked this, so I committed to HEAD.
Comment #13
(not verified) commented