A WordPress-centric search engine for devs and theme authors

site_status_tests › WordPress Filter Hooks

apply_filters( 'site_status_tests', $tests )
  • (array) $test_type { An associative array, where the `$test_type` is either `direct` or `async`, to declare if the test should run via Ajax calls after page load. @type array $identifier { `$identifier` should be a unique identifier for the test that should run. Plugins and themes are encouraged to prefix test identifiers with their slug to avoid any collisions between tests. @type string $label A friendly label for your test to identify it by. @type mixed $test A callable to perform a direct test, or a string AJAX action to be called to perform an async test. @type boolean $has_rest Optional. Denote if `$test` has a REST API endpoint. @type boolean $skip_cron Whether to skip this test when running as cron. @type callable $async_direct_test A manner of directly calling the test marked as asynchronous, as the scheduled event can not authenticate, and endpoints may require authentication. } }
    Required: Yes
Defined at:

Add or modify which site status tests are run on a site.

The site health is determined by a set of tests based on best practices from both the WordPress Hosting Team, but also web standards in general.

Some sites may not have the same requirements, for example the automatic update checks may be handled by a host, and are therefore disabled in core. Or maybe you want to introduce a new test, is caching enabled/disabled/stale for example.

Tests may be added either as direct, or asynchronous ones. Any test that may require some time to complete should run asynchronously, to avoid extended loading periods within wp-admin.


$tests = apply_filters( 'site_status_tests', $tests );