update_status 5.x-2.4

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.
• #243253 by dww: Put in a check while fetching available updates to see if the server was reachable and to bail out before trying to fetch data for all projects if a server is down.
• #431148 by pwolanin, JoshuaRogers, dww: Made it easier to visually distinguish between security updates and regular updates.
• #445748 by dww: Added a hook_update_status_projects_alter() for modules that wish to modify data in update status module.
• #314009 by igor.stamatovski: Added a Macedonian translation.

Known bugs:

• #687368: PHP error after upgrading to version 5.x-2.4

(Sites experiencing this bug should upgrade to version 5.x-2.5)