- 🇺🇸United States dww
Decided to deprecate all the plumbing and remove the UI in 11.2.x.
See 📌 Deprecate/remove the ability to update a module from a URL and authorize.php Active
Closing this as outdated.
Today the IMCE module showed an available update for version 8.x-1.8. The release notes for this version indicate this version as "The last release in 8.x-1.x branch. You can safely upgrade to 8.x-2.x which is Drupal9 compatible". So I can use the /admin/reports/updates/update to update to this version, which I did.
Now the module shows "Also available: 8.x-2.2 (2020-Apr-12)", and indicates "Requires Drupal core: 8.8.5". See the attached screen shot.
I am running Drupal 8.8.5. So, this version is compatible with my system. However, the system GUI (/admin/reports/updates/update) does not allow me to update to this new branch/version. I have to manually install it via composer. This isn't a huge deal, but if you are hosting your site on a service like Pantheon, you need to run composer on your local copy of the site, then use SFTP to move the updated files into place manually. Again, this isn't a massive ordeal, but there doesn't seem to be anything obvious to me that prevents Drupal from recognizing that this update is compatible and therefor allowing it to be installed.
If I am missing something, please let me know. Otherwise, I think Drupal should be enhanced to allow updates to all available compatible versions through the update GUI, even when it means changing branches.
Closed: outdated
11.0 🔥
update.module
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Decided to deprecate all the plumbing and remove the UI in 11.2.x.
See
📌
Deprecate/remove the ability to update a module from a URL and authorize.php
Active
Closing this as outdated.