[wp-trac] [WordPress Trac] #57005: Allow "Persistent Object Cache" and other Site Health options to be dismissable with a checkbox

WordPress Trac noreply at wordpress.org
Fri Nov 11 18:16:54 UTC 2022


#57005: Allow "Persistent Object Cache" and other Site Health options to be
dismissable with a checkbox
-----------------------------+------------------------------
 Reporter:  carlh04426       |       Owner:  (none)
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Site Health      |     Version:  6.1
 Severity:  normal           |  Resolution:  wontfix
 Keywords:  2nd-opinion      |     Focuses:
-----------------------------+------------------------------

Comment (by tigertech):

 As someone who runs a hosting company: I would very much like a way to
 suppress this and similar messages using environment variables (not code).
 It could be similar to the way [https://github.com/WordPress/wordpress-
 develop/blob/6.1/src/wp-includes/functions.php#L7937-L7974
 WP_UPDATE_PHP_URL] works, but with the ability completely suppress the
 test (not just change the recommendation link, although that would also be
 good).

 Why can't we use a filter to suppress the warning? Because we allow people
 to install their own copies of WordPress that don't use our plugin, so we
 can't force filters on everyone.

 More generally, I think that site health suggestions that:

 a) aren't security risks and
 b) can't or shouldn't necessarily even be used on this server

 ... should always be filterable with environment settings.

 In our case, we do offer memcache, but I don't want customers using the
 suggested plugin on [https://wordpress.org/support/article/optimization
 /#persistent-object-cache the page it links to] because it's buggy.

 So the situation is that WordPress 6.1 is showing some people a link to a
 [https://wordpress.org/support/article/optimization/#persistent-object-
 cache page that tells people "ask your hosting provider"], only for many
 hosting companies to tell them "ignore that recommendation, we think it's
 bad advice". That's a poor use of people's time and doesn't build trust in
 either the hosting company or WordPress.

 When this new health recommendation was added, the author clearly realized
 that some people would want to suppress it, because the filtering option
 to do that was included. That's great, but not everyone can force filters
 on their customers. Adding a check of an environment variable, too, would
 be much appreciated for any performance-based recommendations. (I'd be
 happy to provide a patch for this if it might be accepted.)

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


More information about the wp-trac mailing list