[wp-trac] [WordPress Trac] #62304: Enhancement Suggestion/request

WordPress Trac noreply at wordpress.org
Fri Oct 25 21:00:01 UTC 2024


#62304: Enhancement Suggestion/request
---------------------------------------------+-----------------------------
 Reporter:  dimeco                           |      Owner:  (none)
     Type:  enhancement                      |     Status:  new
 Priority:  normal                           |  Milestone:  Awaiting Review
Component:  Site Health                      |    Version:  6.6.2
 Severity:  normal                           |   Keywords:
  Focuses:  ui, administration, performance  |
---------------------------------------------+-----------------------------
 Site health request:

 Could you *PLEASE* add a functionality for us to either "mark as complete"
 for any issue, or "turn off warnings" or "Ignore" or something like that
 for some of the flags? Some are completely irrelevant OR not being used,
 but there's zero way for us to mark it as that.

 i.e., My site status on one of my sites says "Good, but there's still
 things I could do". Why can't I just dismiss those ones I don't want? It
 would be super helpful.

 Example A: Sometimes I get notice that ImageMagik is not installed on the
 site, and it's suggested to be useful. Maybe, but if I am using a site
 that is not image heavy in any way (like a forum), I don't particularly
 care to install it onto my site...

 Example B: Make suggestions on HOW to fix something - i.e., I got a
 “Loopback request” not working error… I have zero clue why it matters or
 how to fix it, the system doesn’t supply anything useful, just gives the
 warning.

 “Loopback requests are used to run scheduled events, and are also used by
 the built-in editors for themes and plugins to verify code stability. The
 loopback request returned an unexpected http status code, 400, it was not
 possible to determine if this will prevent features from working as
 expected.”

 So maybe actually tell people how to fix it? (Might have even been a
 server glitch?)

 Example 3: Some have complained at the ability for Plugins to blatantly
 pitch people to upgrade, acting as if there is a major error in the
 plugin/site unless you do so. (Search the community for Site Health and
 you'll see discussions). My example that triggered all of this - I kept
 having a red flag on the side of my panel for site health. When I read it,
 it was my WishlistMember plugin, stating that I had a legacy version of
 the system and that I needed to upgrade to use Stripe properly.... only I
 DON'T USE Stripe through the plugin. It took a bit, but I figured out
 where to turn stripe off (I never turned it on in the first place at
 install, so this must be something they did).

 I recognize legitimate errors - I completely agree with that. But in
 circumstances like this, when I don't USE stripe for example on the site,
 then I should be able to dismiss something like that with the click of a
 button. (I also already pay every year to WLM for this particular version,
 and I'm not upgrading higher as it isn't necessary for my needs.)

 Some people are starting to view this as almost malicious and intrusive.

 I recognize security issues, or issues that actually affect the site, like
 a plugin failure. But allowing plugins to post messages like this is
 annoying.

 It's not just me, please do a search on Google (not just your own
 community) for people asking how to turn it off or adjust it.

 I believe it is useful and shouldn't be turned off completely. But it
 would be a lot better if it could have an "ignore" toggle on some things.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62304>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list