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 |
|---|---|
| 3467 | |
| 3468 | /** |
| 3469 | * Filters the Heartbeat response sent. |
| 3470 | * |
| 3471 | * @since 3.6.0 |
| 3472 | * |
| 3473 | * @param array $response The Heartbeat response. |
| 3474 | * @param string $screen_id The screen ID. |
| 3475 | */ |
| 3476 | $response = apply_filters( 'heartbeat_send', $response, $screen_id ); |
| 3477 | |
| 3478 | /** |
| 3479 | * Fires when Heartbeat ticks in logged-in environments. |
| 3480 | * |
| 3481 | * Allows the transport to be easily replaced with long-polling. |
| 3482 | * |
| 3483 | * @since 3.6.0 |
| 3484 | * |
| 3485 | * @param array $response The Heartbeat response. |