Make WordPress Core

Opened 3 years ago

Closed 3 years ago

Last modified 2 years ago

#46945 closed enhancement (maybelater)

Site Health: More human readable values

Reported by: birgire Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Site Health Keywords: site-health
Focuses: Cc:


I wonder if the info displayed on the /wp-admin/site-health.php?tab=debug page should be more human readable.

For example:

PHP time limit	90

It might not be obvious to everybody that it's in seconds. What about:

PHP time limit	90 seconds

instead? Similarly:

Max input time	90

We have:

Themes Directory Size	8.56 MB


memory: 2 GB

but we're missing the "Bytes" and the extra space in:

PHP memory limit	512M
Upload max filesize	32M
PHP post max size	32M

It would be great to have unit-consistency here, that would make it easier to understand.

Some of these values originate from e.g. php.ini that uses it's own special formatting, but I wonder if that would be relevant for many users.

Maybe the more technical information/values could be in the "copied" text and
the more human readable values displayed on the admin page?

Attachments (2)

lang.jpg (17.4 KB) - added by birgire 3 years ago.
Language info - before
lang-after.jpg (18.9 KB) - added by birgire 3 years ago.
Language info - after

Download all attachments as: .zip

Change History (6)

3 years ago

Language info - before

3 years ago

Language info - after

#1 @Clorith
3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

The debug information is intended to be technical, it is meant to be shared with a support person or similar, so the primary focus isn't on the human readable aspect of it.

As the values are a direct representation of what they are in various config locations, they really shouldn't be modified in any way either, as it would skewer the data for anyone looking it up with technical insight them selves.

Due to the above, I'm going to mark this as wontfix for now, if anything does come up that indicates it should be otherwise in the future, I'm willing to reconsider at that time though.

#2 @garrett-eclipse
3 years ago

  • Resolution changed from wontfix to maybelater
  • Type changed from defect (bug) to enhancement

#3 @birgire
3 years ago

Thank you for reviewing @Clorith

On the other hand there are already various display values being adjusted to make them more human readable.

For example the values of constants like:

'WP_DEBUG_DISPLAY'    => array(
	'label' => 'WP_DEBUG_DISPLAY',
	'value' => WP_DEBUG_DISPLAY ? __( 'Enabled' ) : __( 'Disabled' ),
	'debug' => WP_DEBUG_DISPLAY,

I found this recent ticket #46909 to Provide a user-friendly value for default comment status. The display value of the default comment status option default_comment_status is now modified with:

'default_comment_status' => array(
	'label' => __( 'Default comment status' ),
	'value' => 'open' === $default_comment_status ? _x( 'Open', 'comment status' ) : _x( 'Closed', 'comment status' ),
	'debug' => $default_comment_status,

Similar for the display of the user_registration option's value. So for different languages these could be very different from the saved DB value.

The PHP config option max_execution_time is displayed as PHP time limit and copied as time_limit, so it's already not an exact one-one relation between the config option and the displayed value.

I wonder if e.g. info bubbles on each item, would be helpful regarding these nuances of displaying human readable info and exact technical info.

#4 @spacedmonkey
2 years ago

  • Component changed from Administration to Site Health
Note: See TracTickets for help on using tickets.