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 |
|---|---|
| 168 | * |
| 169 | * @type string $label The test label, for example `Performance`. |
| 170 | * @type string $color Default `blue`. A string representing a color to use for the label. |
| 171 | * } |
| 172 | * @type string $description A more descriptive explanation of what the test looks for, and why it is important for the end user. |
| 173 | * @type string $actions An action to direct the user to where they can resolve the issue, if one exists. |
| 174 | * @type string $test The name of the test being ran, used as a reference point. |
| 175 | * } |
| 176 | */ |
| 177 | return apply_filters( 'site_status_test_result', call_user_func( $callback ) ); |
| 178 | } |
| 179 | |
| 180 | /** |
| 181 | * Run the SQL version checks. |
| 182 | * |
| 183 | * These values are used in later tests, but the part of preparing them is more easily managed |
| 184 | * early in the class for ease of access and discovery. |
| 185 | * |
| 186 | * @since 5.2.0 |