WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 2398 | * to be called to perform an async test. |
| 2399 | * @type boolean $has_rest Optional. Denote if `$test` has a REST API endpoint. |
| 2400 | * @type boolean $skip_cron Whether to skip this test when running as cron. |
| 2401 | * @type callable $async_direct_test A manner of directly calling the test marked as asynchronous, |
| 2402 | * as the scheduled event can not authenticate, and endpoints |
| 2403 | * may require authentication. |
| 2404 | * } |
| 2405 | * } |
| 2406 | */ |
| 2407 | $tests = apply_filters( 'site_status_tests', $tests ); |
| 2408 | |
| 2409 | // Ensure that the filtered tests contain the required array keys. |
| 2410 | $tests = array_merge( |
| 2411 | array( |
| 2412 | 'direct' => array(), |
| 2413 | 'async' => array(), |
| 2414 | ), |
| 2415 | $tests |
| 2416 | ); |