Changes between Initial Version and Version 6 of Ticket #47058
- Timestamp:
- 05/03/2019 10:24:18 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #47058
-
Property
Status
changed from
newtoclosed -
Property
Summary
changed from
Site Health Check: does not distinguish between production / staging / development sitestoSite Health: does not distinguish between production / staging / development sites -
Property
Milestone
changed from
Awaiting Reviewto - Property Keywords site-health added
-
Property
Resolution
changed from
towontfix
-
Property
Status
changed from
-
Ticket #47058 – Description
initial v6 1 In a ticket focussed on a different issue - https://core.trac.wordpress.org/ticket/47046 - the problem was raised that if `WP_DEBUG` is on, then the "Site Health Check" will raise this as a "critical security" issue. The current justification for that is given in https://core.trac.wordpress.org/ticket/47046#comment:9 is "You should not be running WP_DEBUG on a production site".1 In a ticket focussed on a different issue - #47046 - the problem was raised that if `WP_DEBUG` is on, then the "Site Health Check" will raise this as a "critical security" issue. The current justification for that is given in https://core.trac.wordpress.org/ticket/47046#comment:9 is "You should not be running WP_DEBUG on a production site". 2 2 3 3 However, currently Site Health Check has no concept of whether a site is production, staging or development. It just shows the message.