There is a serious caching bug I reported earlier in update_advanced where the source seems to be update module. You need update_advanced to reproduce this.
Enable Check for updates of disabled modules and themes in admin/reports/updates/settings
and hit Save configuration. After the settings are saved the table on the page is not complete. If you would Save configuration again - you will lose your update_advanced ignore setting for all currently not shown projects.
To prevent the data loss you need to reload admin/reports/updates/settings
as often until the list is complete. This also happens if you have just enabled the update_advanced module or if you change the Check for updates of disabled modules and themes setting. :-(((
The source of this issue seems to be the function update_get_available()
that will not always return a complete list of all modules.
Comments
Comment #1
hass CreditAttribution: hass commentedWe may be able to change the way how update_advanced works. Need to remove
if (isset($available[$key])) {
Comment #2
klonos...coming from #1951408: Core Update manager doesn't correctly handle "status" UPDATE_NOT_CHECKED
Comment #2.0
klonosa
Comment #3
AohRveTPV CreditAttribution: AohRveTPV commentedIs this not a duplicate of #1713276: Doesn't list all modules / lists random modules upon refresh? I cannot reproduce this.
Comment #4
AohRveTPV CreditAttribution: AohRveTPV commentedSeems like a duplicate as mentioned in #3. Please correct if wrong.