[wp-trac] [WordPress Trac] #47046: Site Health: Remove grading

[WordPress Trac]

#47046: Site Health: Remove grading
----------------------------+---------------------------------
 Reporter:  Cybr            |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  site-health     |     Focuses:  ui, administration
----------------------------+---------------------------------

Comment (by arena):

 Replying to [comment:9 earnjam]:


 > Replying to [comment:2 arena]:
 > > => The Info tab is a security issue in itself (too sensitive
 information)
 >
 > This page is only available to administrators. Sensitive information is
 subjective here. >There aren't any passwords, salts, etc included in this
 information. If you're concerned >about what is output, then you can
 filter the response.

 I don't want anyone, (even me) building that room even if there is a lock
 on its door. By the time, this code is in wp, those data can be collected
 (and the use of clipboard.js here is just another security issue)

 >>
 >> > * WP_DEBUG defined and set to true
 > >
 > > the critical issue about the WP_DEBUG and link to "''Read about
 debugging in WordPress''" is just laughable
 >
 > You should not be running WP_DEBUG on a production site

 I don't think that a 127.0.0.1 site is a production site !

 >
 > > ''The REST API request failed due to an error.
 > > Error: [] cURL error 28: Operation timed out after 10000 milliseconds
 with 0 bytes received''
 > >
 > > I am glad to learn that my localhost cannot be accessed by any other
 external website (which ones ? personal data collected ?) !
 >
 > This is just making a `wp_remote_request()` back to your site to test
 that the REST API is accessible. If it isn't, critical parts of WordPress
 may not work, such as the new block editor.
 >
 this has to be documented somewhere. just a question of trust

 > > * Background updates are not working as expected :
 > >
 > > ''Could not confirm that the wp_version_check() filter is available.
 > > (Error) The folder .../wordpress/ was detected as being under version
 control (.svn).''
 > >
 > > This is not an error, it is exactly what i want
 >
 > If this is intentional, then it's safe to ignore or to filter from the
 test list.
 >


 “We can not solve our problems with the same level of thinking that
 created them”
 ― Albert Einstein

 Just put an option in general setting to remove this menu options !

 > > * Your site could not complete a loopback request
 > >
 > > can anyone explain me what is a "wordpress loopback request" (no
 information on that topic in wordpress.org)
 >
 > A loopback is when WordPress makes a request back to itself from within
 a single request. A couple of examples are starting a new `WP_Cron`
 instance, or when editing plugin or theme files through the admin.
 >
 > > => Too regularly, i have to wait 10 seconds for my test/dev site to
 display an admin page,
 > > because Site Health is running !
 > > and my code productivity keeps falling !
 >
 > The Site Health tool code only runs when you load the Site Health page,
 so it would have no affect on any other parts of your admin interface.

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