Hi, I'm having the same issue with Claro (admin theme) on 10.3.6. See attached screenshot. Can you please review and provide a possible solution for Claro as well? Thank you.
- 🇩🇪Germany sachbearbeiter
Is there any hope of finding this must-have feature in a release? I have no idea why Drupal is built on a modern PHP codebase and it is still not possible to provide basic UI functionalities for the editorial team?
- 🇺🇸United States dww
I opened an MR to get started on #3483501, but there are a bunch of open questions in the issue for release and/or framework managers to weigh in on. Thanks!
- 🇬🇧United Kingdom catch
Opened 📌 Rename update module back to Update Status Active .
- 🇺🇸United States dww
https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/updat...
name: 'Update Manager' type: module description: 'Checks for updates and allows users to manage them through a user interface.' …
- 🇬🇧United Kingdom catch
Option #2 sounds good. I know the authorize.php-related stuff was called update manager, but completely missed that was the human readable module name too.
- 🇭🇺Hungary Gábor Hojtsy Hungary
Indeed, good point! I think renaming the existing one's human readable name back to Update Status is a good way forward. Internally it reflects that naming already.
- 🇺🇸United States dww
To vote on my own poll from the previous comment, I’m totally fine with option #2 and changing the human readable name of update.module back to “Update status”, add CR and release notes, fix documentation, and hope for the best that it won’t be too confusing. But I don’t personally have time or any funding to do all that work myself. so if y’all decide that’s best, I’d appreciate some help getting it all done. Thanks!
- 🇺🇸United States dww
+1 to not calling the new thing “auto”. Side note, +1 to make it so it can be configured to only update when a human says so, and never “automatically”.
However, for what it’s worth, “Update Manager” is already the human name for update.module in core. Once upon it time (D5 contrib) it was called “Update status”. When moved into core in D6, Dries wanted it called “Update Manager” since he had dreams of it actually updating your site. Those dreams were (partially) realized in D7 when we added all the authorize.php stuff and contrib updating. The machine name is still only
update
, but help text, .info.yml name, and reams of documentation and countless issues & comments all call it “Update manager”.So, if we go forward calling the renamed auto_updates “Update manager”, we have to pick from:
- We’re okay calling two different modules with different responsibilities the same thing. 😬
- We should rename update.module back to “Update status” in UI text and documentation (#NeedsFollowup). Once this lands, and we finish ripping out the authorize.php parts, providing “status” is all update.module will be responsible for again.
- Or we pick a different new name for auto-updates.
- 🇭🇺Hungary Gábor Hojtsy Hungary
Update Manager sounds good and is in line with the rest of the core and contrib features in this area. Also with Package Manager.
- 🇬🇧United Kingdom catch
✨ Add Alpha level Experimental Package Manager module Needs review is in.
At and after DrupalCon Barcelona, we discussed that instead of renaming 'Automatic updates' to 'auto_updates' for core, we should instead rename it to 'Update Manager'. The main reason for this was that a lot of experienced developers are sceptical about 'automatic updates' in the sense of unattended, and might not even look at this if they assume all it does. But the module also does 'attended updates' which will run the various composer commands locally, and then developers can commit composer.lock changes and deploy from their without anything automatic happening on production. Update manager is more neutral from that standpoint.
- 🇺🇸United States joshuasosa
Also tested #466 and have the same issue with it as #467 on Drupal 10.3.6. I moved around the filter order and cleared cache with no success.
Automatically closed - issue fixed for 2 weeks with no activity.