apply_filters( 'site_status_tests', array $test_type )
Add or modify which site status tests are run on a site.
Description Description
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.
Parameters Parameters
- $test_type
-
(array) An associative array, where the
$test_type
is eitherdirect
orasync
, to declare if the test should run via Ajax calls after page load.- 'identifier'
(array)$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.- 'label'
(string) A friendly label for your test to identify it by. - 'test'
(mixed) A callable to perform a direct test, or a string AJAX action to be called to perform an async test. - 'has_rest'
(boolean) Optional. Denote if$test
has a REST API endpoint. - 'skip_cron'
(boolean) Whether to skip this test when running as cron. - 'async_direct_test'
(callable) A manner of directly calling the test marked as asynchronous, as the scheduled event can not authenticate, and endpoints may require authentication.
- 'label'
- 'identifier'
Source Source
Changelog Changelog
Version | Description |
---|---|
5.6.0 | Added the async_direct_test array key. Added the skip_cron array key. |
5.2.0 | Introduced. |
User Contributed Notes User Contributed Notes
You must log in before being able to contribute a note or feedback.
Example usage to remove a test:
Also check out the Site Health Manager plugin that allows you to easily remove custom status test using this hook.
Here’s a quick one-liner to disable 3 Site Health tests that tend to be false alarms. You can drop it into a plugin or your theme’s
functions.php
.Feedback
The PHP Version may be out of direct control of the user, but they should still know if they need to contact a host about getting it updated. And having a public .git directory is a problem, and should be warned about. There are security implications. In summary, best to not just disable tests because they are failing :) — By Caleb Burks —