[wp-trac] [WordPress Trac] #49923: Change "Critical Issue" to "Recommendation"

WordPress Trac noreply at wordpress.org
Sat Apr 25 18:41:03 UTC 2020


#49923: Change "Critical Issue" to "Recommendation"
--------------------------+------------------------------
 Reporter:  La Geek       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Site Health   |     Version:  5.4
 Severity:  critical      |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by La Geek):

 Replying to [comment:1 Clorith]:
 > Hmm, although I would argue that you could filter out the tests if
 you're familiar with what you are doing... I do have a different thought
 here though.

 Sure, for upcoming client websites. But past client websites where you
 don't have any access anymore ... most of my clients want to update and
 manage their websites themselves ¯\_(ツ)_/¯ but get panic with this new
 site health widget.
 >
 > We could check if minor updates are still allowed to run automatically,
 if they can, the severity could be lowered to a recommendation, but having
 automatic security updates completely disabled should still give a
 critical error in my opinion, as unknowing users might have changed values
 based on recommendations without knowing what they do, while those that do
 know what they do and are aware may ignore the output of this check (or
 use one of the plugins that filters it away).
 >
 > Thoughts?

 If minor updates are allowed, you don't need any hint at all (or do I
 mistunderstand?)

 A recommendation, when automatic updates are filtered out, is enough
 (imo). The hint text should be changed and explain more.

 And it is no error. The filters and constants are valid.

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


More information about the wp-trac mailing list