'Install new module' (theme) link requires 'Clear all caches' or update.php after enabling core module 'Update manager' [#2809957]

The 'Install new module' button/link will not appear on the 'Extend' page (nor will the 'Install new theme' button/link appear on the 'Appearance' page) after enabling the core module 'Update manager', unless either 'Clear all caches' is done next; or the update script is run (update.php).

Is this normal Drupal 8 behavior?

I would say that even if it is normal, for newbie Drupal users it would be an unexpected situation, and one that they would not intuitively know how to respond to.

---

The 'Update manager' will not have been enabled if, during the browser-based Drupal 8 installation, the user did not leave the check-mark for the box "Check for updates automatically"

---

The solution for this current situation is clearly detailed at:

"Installing contributed modules: Find, import, enable, configure"

https://www.drupal.org/node/1897420/edit

...but, should we expect users to know that 'Clear all caches' or update.php are required?

Comments

Comment #1

2 October 2016 at 00:50

Christopher James Francis Rodgers created an issue. See original summary.

Comment #2

2 October 2016 at 00:50

Version:

8.3.x-dev

» 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.

Comment #3

2 October 2016 at 00:50

Version:

8.4.x-dev

» 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now 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.

Comment #4

2 October 2016 at 00:50

Version:

8.5.x-dev

» 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.

Comment #5

2 October 2016 at 00:50

Version:

8.6.x-dev

» 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now 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.

Comment #6

2 October 2016 at 00:50

Version:

8.7.x-dev

» 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Comment #7

2 October 2016 at 00:50

Version:

8.8.x-dev

» 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Comment #8

2 October 2016 at 00:50

Version:

8.9.x-dev

» 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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.