Would it be possible for Release Monitor to check the status of non-enabled modules? I have a multi-site installation and every site has different enabled modules, but I can't always check every site's release monitor. It would be nice to have an option to check releases of non-enabled modules.
Comments
Comment #1
douggreen commentedThanks for the suggestion! However, I'm not inclined to implement. With the Drupal 6 code freeze is about 3 months away, I'd like to limit the new features for releasemonitor. I'd like to significantly rework this module with the hopes of adding some of it to Drupal core.
If I did implement this, I'd want the settings form to allow a user to check "all", "active", or select from a list of modules (similiar to how I implemented settings for coder).
I have concerns that this would cause additional overhead on d.o (or c.d.o) for modules that aren't even used!
Comment #2
ray007 commentedI agree that this would be a useful feature for 2 reasons:
I sometimes test a module, find out it's not yet ready to use and disable it again. Would be good to see availability of new versions.
Load on drupal.org: as the original poster said, he wants to check releases for a multisite installation in a singe place, he'll probably also have only 1 releasemonitor active instead of 1 for each site ...
Comment #3
fm commentedfwiw, i have several non-enabled modules in my module directory. They're there because I am hoping to get them working someday and, in most cases, this means waiting for an upgrade that corrects bugs. Scanning for upgraded modules that are not enabled is very valuable ... heck, one might argue that it's more important than scanning for upgrades for enabled modules.
But really, I'd like to be notified of upgrades for any module (both enabled and not) that I have in my modules directory. As a matter of routine practice, I delete the truly useless modules from the server.
Comment #4
douggreen commentedI'm closing all release monitor issues. Please see the update status project instead.