[wp-trac] [WordPress Trac] #47644: Improve wording for PHP update warning in Site Health

[WordPress Trac]

#47644: Improve wording for PHP update warning in Site Health
-------------------------------------------------+-------------------------
 Reporter:  danieltj                             |       Owner:  marybaum
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.3
Component:  Site Health                          |     Version:  5.2
 Severity:  minor                                |  Resolution:
 Keywords:  has-patch needs-testing has-copy-    |     Focuses:
  review                                         |
-------------------------------------------------+-------------------------

Comment (by marybaum):

 Replying to [comment:22 garrett-eclipse]:

 Ah. I think I conflated several different labels.

 Let's try this in the description:

 {{{#!php
 <?php
 PHP is the programming language developers use to build and maintain
 WordPress. Newer versions of PHP are faster and more secure, so staying up
 to date ''[ no hyphens bc after the verb ]'' will help make your site
 faster and more secure, too. You should be running at least version %s.
 }}}


 Label for is_secure:

 {{{#!php
 <?php
 Your version of PHP (%s) needs an update.
 }}}


 Label for no-longer-secure versions:

 {{{#!php
 <?php
 Your version of PHP (%s) is not secure and needs an update.
 }}}




 > Thanks @marybaum I appreciate the feedback.
 >
 > While more clear that is a little too verbose for the accordion label
 here.
 >
 > I've taken another attempt here
 [https://core.trac.wordpress.org/attachment/ticket/47644/47644.4.diff
 47644.4.diff] and below is a summary of strings in my current patch (%s
 refers to version string), would love your thoughts @marybaum;
 > - Description (Used in all types of this test result);
 > `PHP is the programming language used to build and maintain WordPress.
 Newer versions of PHP are both faster and more secure, so staying up to
 date will have a positive effect on your site’s overall performance
 and security. The minimum recommended version of PHP is %s.`
 > - Label for up to date;
 > `Your version of PHP (%s) is up to date`
 > - Label for is_supported when older than recommended but still receiving
 active support;
 > `Your version of PHP (%s) is out of date`
 > - Label for is_secure when their version is only receiving security
 fixes
 > `Your version of PHP (%s) should be updated`
 > - Label for no longer secure versions;
 > `Your version of PHP (%s) requires an update`
 > *The main verbiage change I did was minimal to avoid the 'We' and switch
 recommend to just indicating their version is no longer up to date.
 > *I've also moved the version number to tie it directly to PHP, and
 updated the WordPress version string to match. This maps the version
 directly to the word it's meant for avoiding confusion. I did preserve the
 version in the label as it's already in convertion for WP version and I
 felt it more useful at a glance as once users have read the description
 they'll most likely skip it due to content fatigue, best to have it
 prominent.
 > *Overall I tried to avoid a large rewrite and just address the point on
 'power' and 'we', and added 'security' to the description.
 >
 > Note: Thanks @SergeyBiryukov I did switch back from 'power WordPress' to
 'build and maintain WordPress'
 >
 > Would love feedback and testing so this can be committed before Monday.
 @clorith / @afragen / @SergeyBiryukov / @danieltj  / @marybaum
 >
 > Cheers

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47644#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform