Disabled update module shouldn't produce a status report warning

Created on 13 April 2017, about 7 years ago
Updated 24 June 2024, 4 days ago

On the status report, if you have uninstalled the Update module you will get a big scary warning:

Update notifications are not enabled. It is highly recommended that you enable the Update Manager module...

There are many situations where it's perfectly reasonable to disable the update module, such as in an enterprise environment where you monitor for updates via other dedicated means and don't want the performance impact of having Update enabled in production. In these cases, the warning is just a distraction and contributes to a "crying wolf" mentality.

Ideally, there would be a way for expert administrators to disable this warning.

✨ Feature request
Status

Needs work

Version

11.0 🔥

Component
System  →

Last updated about 10 hours ago

No maintainer
Created by

🇺🇸United States Dane Powell

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇳India smitghelani

    Re-roll for Drupal 10.3.x.

  • 🇮🇳India smitghelani

    Re-roll for 10.3.x branch, above one has little issue in finding file.

  • All issues should target the 11.x branch.

  • In addition, there is a merge request open, so please refrain from making changes by submitting patches. It's hard to see what changed without an interdiff, and the pipeline won't run.

  • Facing issues here, not getting edit button while trying to target existing MR against 11.x

    Even facing issue while creating new branch against 11.x :
    Not able to search branch 11.x

    Already 11.x selected however when create new button, getting error:
    Failed to create branch '2869592-disabled-update-module-status': invalid reference name '11.x'

  • Pipeline finished with Success
    7 days ago
    Total: 608s
    #204292
  • 🇳🇿New Zealand quietone New Zealand

    @smitghelani, @solideogloria, @pooja_sharma, @hswong3i. It is an important part of working on an issue to read the comments and the issue tags to determine what to do. Not all issues at needs work needs an MR updated. And comment #39 and #40 explained that the approach here is not acceptable. This was stated again in #60. The work here is an issue summary update and to provide the information asked for in #39.

  • Okay @quietone got your concerns, Thanks for flagging it out along with constructive feedback, recently I just have started exploring contribution. As this issue comments are too long due to which some comments that needs to be addressed remain unnoticed unintentionally, however try to make it sure contribute meaningfully in the right direction

    I agree with #39 & #40, maybe it's best to think of something else instead of hide the warnings information from core itself, especially from a security perspective where transparency & awareness of potential risks are crucial.

    If this request still needs, then I believe suggested one contrib module approach 'll fit well in this scenario.

Production build 0.69.0 2024