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 |
|---|---|
| 1381 | * an associative array that is displayed as name/value pairs. |
| 1382 | * @type string $debug Optional. The output that is used for this field when the user copies the data. |
| 1383 | * It should be more concise and not translated. If not set, the content of `$value` is used. |
| 1384 | * Note that the array keys are used as labels for the copied data. |
| 1385 | * @type boolean $private Optional. If set to `true` the field will not be included in the copied data |
| 1386 | * allowing you to show, for example, API keys here. |
| 1387 | * } |
| 1388 | * } |
| 1389 | */ |
| 1390 | $info = apply_filters( 'debug_information', $info ); |
| 1391 | |
| 1392 | return $info; |
| 1393 | } |
| 1394 | |
| 1395 | /** |
| 1396 | * Format the information gathered for debugging, in a manner suitable for copying to a forum or support ticket. |
| 1397 | * |
| 1398 | * @since 5.2.0 |
| 1399 | * |