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 |
|---|---|
| 2724 | |
| 2725 | /** |
| 2726 | * Filter the Heartbeat response sent. |
| 2727 | * |
| 2728 | * @since 3.6.0 |
| 2729 | * |
| 2730 | * @param array $response The Heartbeat response. |
| 2731 | * @param string $screen_id The screen id. |
| 2732 | */ |
| 2733 | $response = apply_filters( 'heartbeat_send', $response, $screen_id ); |
| 2734 | |
| 2735 | /** |
| 2736 | * Fires when Heartbeat ticks in logged-in environments. |
| 2737 | * |
| 2738 | * Allows the transport to be easily replaced with long-polling. |
| 2739 | * |
| 2740 | * @since 3.6.0 |
| 2741 | * |
| 2742 | * @param array $response The Heartbeat response. |