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 |
|---|---|
| 2132 | |
| 2133 | /** |
| 2134 | * Filter the Heartbeat response sent. |
| 2135 | * |
| 2136 | * @since 3.6.0 |
| 2137 | * |
| 2138 | * @param array|object $response The Heartbeat response object or array. |
| 2139 | * @param string $screen_id The screen id. |
| 2140 | */ |
| 2141 | $response = apply_filters( 'heartbeat_send', $response, $screen_id ); |
| 2142 | |
| 2143 | /** |
| 2144 | * Fires when Heartbeat ticks in logged-in environments. |
| 2145 | * |
| 2146 | * Allows the transport to be easily replaced with long-polling. |
| 2147 | * |
| 2148 | * @since 3.6.0 |
| 2149 | * |
| 2150 | * @param array|object $response The Heartbeat response object or array. |