[wp-trac] [WordPress Trac] #47223: Site Health Check: "last missed cron" test too aggressive

[WordPress Trac]

#47223: Site Health Check: "last missed cron" test too aggressive
-------------------------------------------------+-------------------------
 Reporter:  DavidAnderson                        |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Site Health                          |     Version:  5.2
 Severity:  normal                               |  Resolution:
 Keywords:  site-health needs-testing has-patch  |     Focuses:
-------------------------------------------------+-------------------------

Comment (by galbaras):

 @peterwilsoncc Why not make it a constant, given that WP CRON is disabled
 via wp-config.php?

 **Simple idea**

 `define( 'WP_CRON_INTERVAL', 15 ); // Minutes`
 or
 `define( 'CLI_CRON_INTERVAL', 15 ); // Minutes`

 **Radical idea**

 Repurpose DISABLE_WP_CRON to `define( 'DISABLE_WP_CRON', 15 );`.

 The logic can be like this:

 - If `DISABLE_WP_CRON` is some positive integer (maybe within a reasonable
 range), the default WP_CRON will be disabled and Site Health will use it
 as the interval.

 - If `DISABLE_WP_CRON === false`, the normal WP_CRON will be used and Site
 Health will use its default interval for that.

 - Otherwise, WP_CRON will be disabled and Site Health will use a
 (different?) default value for the interval.

 Doing this may actually help plugins and custom functions tailor various
 intervals to the specific sites. For example, admins will not be offered
 1-minute and 5-minute intervals when they don't make sense for the site.

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