![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 5 years ago
Last modified 5 years ago
#54017 new feature request
Add an Update Log (to site health?)
| Reported by: | Ipstenu | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Site Health | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
As of the last few major releases, WordPress _auto updates_ major releases.
I am 100% for this, however I've found it can be a total pain to try and figure out why someone was updated sometimes. Not to mention people are now getting updates with only the email as a notice, which means sometimes the non-primary admin will find a problem first and have no clue why.
This could be alleviated if we had an update log, possibly in site health, that recorded...
- When WP was installed (this will allow you to back track "Oh you started on WP 5.9, that means...")
- When a plugin or theme is updated
- When WP is updated
That also lets people keep tabs on when things happened if their email is down or they got shunted to spam.
There are a number of plugins that do this, but having it in core allows it to be utilized by web hosts and wp-cli natively.
