[wp-trac] [WordPress Trac] #61251: Prevent Plugins adding warnings in the Site Health
WordPress Trac
noreply at wordpress.org
Mon May 20 23:19:32 UTC 2024
#61251: Prevent Plugins adding warnings in the Site Health
-------------------------+----------------------
Reporter: Marc4 | Owner: (none)
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Site Health | Version:
Severity: normal | Resolution: wontfix
Keywords: | Focuses:
-------------------------+----------------------
Changes (by peterwilsoncc):
* status: new => closed
* resolution: => wontfix
* milestone: Awaiting Review =>
Comment:
Hi @Marc4 and thanks for the ticket.
I agree that an upgrade to pro item is a questionable use of the Site
Health screen. I couldn't agree more, in fact.
However, I think that removing the filters that allow plugins to add items
to the Site Health screen would create more problems than it would solve.
There are more legitimate uses of the Site Health report for plugins than
not. Some example I can think of are:
* caching plugins warning that there is no redis/memcache server to
connect to
* SASS plugins reporting the need to connect to a service, ie Item one in
your ticket
* 2FA plugins warning that administrator level accounts do not have 2FA
enabled
Unfortunately WordPress has no way of detecting whether a site health item
is useful or questionable in nature so I'm going to close this ticket as
unplanned (wontfix).
The WordPress plugin repository has guidelines on what plugins can and can
not do. You may wish to open a ticket to discuss adding/clarifying
policies around the use and abuse of the Site Health report. You can do
that on [https://github.com/WordPress/wporg-plugin-guidelines/issues the
plugin guidelines issue tracker]
--
Ticket URL: <https://core.trac.wordpress.org/ticket/61251#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list