I think this happened after the last core update, but I cannot remember when that was, sorry.

no versions in available updates pages

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

klonos’s picture

Title: (dev) version numbers not shown any more in the "Available updates" page (regression?) » (dev) version numbers and dates missing from modules listed in the "Available updates" page (regression?)

...it's been so long since I filed this one and I'm not around d.o lately so that I forgot about it and went on and filed a dupe #1907120: Dev version and date missing from modules listed in the "Available updates" page.. Sorry.

Anyways, am I the only one seeing this?

klonos’s picture

Component: update.module » base system

...wrong component perhaps?

dww’s picture

Component: base system » update.module

No, you had the right component. I'm just way behind on D8 in general, and Update manager in particular. If anyone else can confirm the bug, that'd be a good start.

Thanks/sorry,
-Derek

klonos’s picture

With the latest dev the issue gets even worse:

just got worse

Notice the "Unknown release date" and no other modules listed despite the fact that I have enabled the "Check for updates of disabled modules and themes" option under settings (/admin/reports/updates/settings) and I have at least admin_menu installed + a few other modules in my /modules directory that should be listed. Only core is listed instead and despite the fact that it is updated to the latest dev available, it still shows up as not up to date.

klonos’s picture

Title: (dev) version numbers and dates missing from modules listed in the "Available updates" page (regression?) » (dev) version numbers and dates missing from modules listed in the "Available updates" page (regression)

I'm surprised that no one else has this issue! Am I the only person looking in the "Available updates" page in order to download updates?

Anyways, I don't know if this counts as confirmation, but since past December (when I originally filed this issue) I must have rebuilt from scratch at least 3 D8 dev servers more than half a dozen times each (due to core2core updates resulting in WSOD). Each time the same issue on all these installations and since sometime past moth there is even no display of contrib modules shown on the page either.

wusel’s picture

Priority: Normal » Critical
Issue tags: +Update manager

I have this issue too with serveral D8-dev-versions in the past.

i think, a regession is critical.

Wusel

klonos’s picture

Priority: Critical » Normal
Issue tags: +Regression

nope:

Critical

Critical bugs either render a system unusable (not being able to create content or upgrade between versions, blocks not displaying, and the like), cause loss of data, or expose security vulnerabilities. These bugs are to be fixed immediately.

...

Major

Issues which have significant repercussions but do not render the whole system unusable are marked major. An example would be a PHP error which is only triggered under rare circumstances or which affects only a small percentage of all users.

...

Normal

Bugs that affect one piece of functionality are normal priority. An example would be the category filter not working on the database log screen. This is a self-contained bug and does not impact the overall functionality of the software.

Trust me. I want this fixed badly too (I was the one to file this issue), but bumping priority is not the way to do it. Besides, if it was either major or critical, we'd have way more than 4 people following here ;)

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Issue summary: View changes
Status: Active » Closed (cannot reproduce)
Issue tags: +Bug Smash Initiative
FileSize
45.64 KB

@klonos, thank you for reporting this problem.

Tested on 8.9.x, with a standard install and then used composer to get an old version of admin_toolbar. Navigated to /admin/reports/updates and the display does not show the error in the IS.

Therefore, closing as cannot reproduce. If you are experiencing this problem reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").

Thanks!