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 |
|---|---|
| 2564 | |
| 2565 | /** |
| 2566 | * Filter the Heartbeat response sent. |
| 2567 | * |
| 2568 | * @since 3.6.0 |
| 2569 | * |
| 2570 | * @param array|object $response The Heartbeat response object or array. |
| 2571 | * @param string $screen_id The screen id. |
| 2572 | */ |
| 2573 | $response = apply_filters( 'heartbeat_send', $response, $screen_id ); |
| 2574 | |
| 2575 | /** |
| 2576 | * Fires when Heartbeat ticks in logged-in environments. |
| 2577 | * |
| 2578 | * Allows the transport to be easily replaced with long-polling. |
| 2579 | * |
| 2580 | * @since 3.6.0 |
| 2581 | * |
| 2582 | * @param array|object $response The Heartbeat response object or array. |