Active
Project:
Drupal core
Version:
main
Component:
system.module
Priority:
Normal
Category:
Plan
Assigned:
Unassigned
Reporter:
Created:
9 May 2017 at 20:39 UTC
Updated:
2 Jun 2025 at 23:40 UTC
Jump to comment: Most recent
The status report may include too many warnings that are not actionable, or that warn when they should merely inform.
For example:
Evaluate warnings in core, and determine which should be:
Fewer unneeded and unheeded warnings.
Depends on child issue
Depends on child issue
Comments
Comment #2
danepowell commentedComment #3
Anonymous (not verified) commentedThis is a very doubtful undertaking. Perhaps it is worth implementing via a contrib module, although I would not like to get a project in which this module is enabled.
AFAIK, Notice for this.
Understand correctly, the temptation to abuse this feature is too great :)
Comment #4
japerry+1 to vaplas, the impression you're getting is because of the plethora of bad warnings we have in core. In fact, what you see as warnings really should be items that are definitely wrong. If they aren't, then they aren't warnings.
PHP definiton of warnings:
Looking back at your examples, disabling update module should not throw a warning. The config module probably should not throw a warning either. (although that one is more debatable, and is based on environment context)
I don't believe that warnings should be suppressed, but rather we should be critical about what modules are throwing warnings and fix them. I'll make some followup issues accordingly.
Comment #5
catchThis was discussed in the original issue that added the warning iirc. At least, webchick wrote a module fixing this exact use case, it's been around since 2007. Just needs porting to 8.x: https://www.drupal.org/project/update_notifications_disable
Comment #6
xjmAh, I see what happened. @catch closed this issue, rather than the other one.
Let's rescope this issue to be a meta for the child issues @japerry wanted to file? Then I'd maybe "works as designed" #2869592: Disabled update module shouldn't produce a status report warning.
Comment #7
xjmWell, for now adding #2869592: Disabled update module shouldn't produce a status report warning to the summary with my notes.
Comment #8
xjmComment #9
xjmComment #10
danepowell commentedKeep in mind also that the severity of an issue might vary based on environment, and even "obvious" warnings and errors like the update status warning or update.php free access error should legitimately be suppressed at times, such as on a local environment.
Comment #12
xjm#2830880: Warn site admins when composer dev dependencies are installed inside of docroot is another one where the consequences could be severe enough to actually merit a warning -- even though there's not necessarily something wrong with dev dependencies being installed in the docroot, the past consequences (RCE vulnerability) are severe enough that I think a warning is still merited. While it's not "wrong" per se on a local development environment, it's something you need tobe warned to address before putting a site into production.
Comment #13
xjmComment #17
danepowell commentedComment #26
mstrelan commentedIMO this should probably be postponed on #2880439: Status report requirements should be more defined. We can't evaluate what status each requirement should be if the definition of the statuses isn't well defined.