- 🇺🇸United States dww
Now that 📌 Deprecate/remove the ability to update a module from a URL and authorize.php Active and child issues are done, all this code is deprecated and will be removed in D12.
Although there is "Manual updates required" section in modules' update form - it sounds like hardcoded to be used for core updates only.
If we programmatically move some modules to this section marking them for manual update... if core is up-to-date and one of our manual-marked modules is not - the subtitle of the section will still display: "Automatic updates of Drupal core are not supported at this time." which may confuse somebody if drupal core will not be listed as outdated below.
Example is described in comment #16 here: #2883380-16: Exclude Ludwig-managed modules from Update Manager →
Move hardcoded "Automatic updates of Drupal core are not supported at this time." notice away from the title section.
Place the notice somewhere inside "Manual updates required" table just above Drupal Core row - if Drupal core is listed for update only.
Adjust code at core/modules/update/src/Form/UpdateManagerUpdate.php so that contrib modules can easily take advantage of manual updates option just like Drupal core.
Decide what to do...
Closed: won't fix
11.0 🔥
update.module
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Now that 📌 Deprecate/remove the ability to update a module from a URL and authorize.php Active and child issues are done, all this code is deprecated and will be removed in D12.