Opened 6 years ago
Closed 4 years ago
#50934 closed defect (bug) (duplicate)
Site Health => Background Updates
| Reported by: | jamesmorrison | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Site Health | Version: | 5.3 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
The Site Health => Background Updates shows a "critial security issue", because I have disabled background updates. The output also notes that WordPress is version controlled via Git.
This is not a "critical security issue" - this is exactly how I have set up the site, and treats a version controlled instance as a problem. The same checks also noted that the site is running WP 5.5 (released yesterday).
Where a site is noted as being version controlled, it's a reasonable expectation that the people operating it have done so intentionally, and don't need a "critical security issue" alert which it clearly isn't.
Proposal: where a site is version controlled, by all means note that this is detected but make this "info" level, not "critical security issue".
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Previously #47982.