Releases for Update Status

Bugs fixed since version 5.x-2.3:

• #155450 by JoshuaRogers, dww: Moved cached data into a separate table in the database using a private (non-volatile) cache API (#220592 backport).
• #267724 by dww: Fixed bug where update_status was not checking for new data when the cache was cleared, until the set time was elapsed. Now update_status checks on cron after the cache was cleared.
• #386636 by dww: Fixed bug where the settings to ignore certain projects would not take effect in some cases when modules were marked unsupported by the maintainer.
• #499828 by Dave Reid: Fixed release date on multi-module projects to always use the most recent datestamp, not the first datestamp we find.
• #319033 by Dave Reid, Ralf, dww: Fixed the order of the "Available updates" report so that it is sorted by project name, not by the names of modules included in each project.

Other changes since version 5.x-2.3:

• #162788 by dww, Dave Reid, JohnAlbin: Added a setting to check update status on disabled modules.

Changes since 5.x-2.1:

This is the first official, stable release of the the 5.x-2.* series. This is very similar to the code that is now in the 6.x series of Drupal core. This contains numerous improvements over the 5.x-1.* series:

This is a (hopefully final) release candidate (RC) before the official 5.x-2.0 release. At this point, no new features will be added. Changes since 5.x-2.0-beta2:

Changes since update_status 5.x-1.2

Version 1.1 of the update status module will try to guess at the project your modules from CVS come from (as well as very old modules from drupal.org); it also allows you to turn off notification for particular modules. It also fixes some UI bugs and adds functionality to the interface.

Version 1.2 fixes the notification part of this, which was a little bit broken.