#56378 closed enhancement (fixed)
Display date of Site health report creation
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 6.3 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Site Health | Keywords: | has-patch has-screenshots needs-testing |
Focuses: | Cc: |
Description
Hello,
Site Health is full of great info when, like me you're doing support all the days.
I think the creation date is missing because WordPress user are installing / removing / updating Core, plugins and theme and we need to know what was the date the report has been created.
This Trac ticket and the patch will add this information.
Attachments (6)
Change History (30)
#1
@
16 months ago
I wonder if "Generation Date" instead of "Creation date" and "Generated" instead of "creation_date" shouldn't be better
#2
@
15 months ago
Interesting thought, I'm not sure a new section is the right approach for this information though, but i do see its value from a support perspective.
What if it instead included something like like "Current server time", and "Current UTC time" under the "Server" section? That would both give you the current time, the server time, allow for comparison if there's some time-related issues, but still provides the information?
I'd also love to see the debug field be populated with an ISO 8601 formatted data, that isn't dependent on the configured date format of the site. (that would be the YYYY-MM-DD
formatting, optionally with the current time added as well if that makes sense).
#3
@
15 months ago
Hello,
Thanks @Clorith for your review and ideas.
I add a new patch Add-Date-56378.patch with your idea.
This ticket was mentioned in Slack in #core by sebastienserre. View the logs.
6 months ago
#7
@
6 months ago
The logic of the latter patch looks good to me at a glance.
Let's put together a GitHub pull request to ensure tests are passing (I think we have a few coding standards issues to fix).
#8
@
6 months ago
- Keywords has-screenshots added
Add-Date-56378.patch
- copy from clipboard:
current: 2023-06-15T10:19:31+00:00 utc-time: Thursday, 15-Jun-23 10:19:31 UTC server-time: 2023-06-15T10:19:29+00:00
This ticket was mentioned in PR #4620 on WordPress/wordpress-develop by @audrasjb.
6 months ago
#9
#10
@
6 months ago
- Keywords 2nd-opinion removed
- Milestone changed from Future Release to 6.3
PR4620 refreshes the patch against trunk and fixes various coding standard issues.
Moving for 6.3 consideration.
#11
@
6 months ago
OK, so the patch always work, I've tested with the beta test plugin set to update to the nightly release...
NodeJS is insulting me when I try to build WordPress-develop... I will dig in this soon
#13
@
6 months ago
Test Report
This report validates that the indicated patch addresses the issue.
Patch tested: https://github.com/WordPress/wordpress-develop/pull/4620
Environment
- OS: macOS 13.2.1 (22D68)
- Web Server: Nginx
- PHP: 7.4.30
- WordPress: 6.3-alpha-55505-src
- Browser: Chrome 114.0.5735.106
- Theme: Twenty Twenty-Three
- Active Plugins:
- No plugins activated
Actual Results
- ✅ Expected result works as expected with patch.
Additional Notes
- Tools => Site Health => Info => Server displays
Current date
,Current UTC time
,Current Server time
Supplemental Artifacts
Before: https://d.pr/i/XlRhFm
After: https://d.pr/i/DqYYtM
@Hareesh Pillai commented on PR #4620:
6 months ago
#14
The label Current date
should read Current time
, as the value displays date and time as well.
@sebastienserre commented on PR #4620:
6 months ago
#15
@audrasjb I'm not sure how to improve this PR with @hareesh-pillai suggestion as the branch is on your side :pensive:
If I can help, feel free to ping.
@audrasjb commented on PR #4620:
6 months ago
#16
Hey @sebastienserre feel free to add a new patch in the ticket. Then I can port it to my PR so we can run unit test on it :)
@
6 months ago
Add suggestion made at https://github.com/WordPress/wordpress-develop/pull/4620#issuecomment-1593110036
@audrasjb commented on PR #4620
5 months ago
#18
#20
@
5 months ago
Test Report
This report validates that the indicated patch addresses the issue.
Patch tested: https://github.com/WordPress/wordpress-develop/pull/4620
Environment
- OS: macOS 12.6.7
- Web Server: Nginx
- PHP: 7.4.33
- WordPress: 6.3-alpha-55505-src
- Browser: Brave 1.52.126
- Theme: Twenty Twenty-Three
- Active Plugins: No plugins activated
Actual Results
- ✅ Issue resolved with patch.
Additional Notes
- we got Current time, Current UTC time, Current Server time from Tools->Site Health-> Info-> Server
Supplemental Artifacts
Before: https://prnt.sc/tY_st3Ccuh4H
After: https://prnt.sc/PO4icw85a5-d
This ticket was mentioned in Slack in #core by chaion07. View the logs.
5 months ago
#22
@
5 months ago
- Owner set to audrasjb
- Resolution set to fixed
- Status changed from new to closed
In 56056:
@audrasjb commented on PR #4620:
5 months ago
#23
committed in https://core.trac.wordpress.org/changeset/56056
Site health extraction