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 |
|---|---|
| 2080 | $screen_id = sanitize_key($_POST['screen_id']); |
| 2081 | else |
| 2082 | $screen_id = 'front'; |
| 2083 | |
| 2084 | if ( ! empty($_POST['data']) ) { |
| 2085 | $data = (array) $_POST['data']; |
| 2086 | $response = apply_filters( 'heartbeat_received', $response, $data, $screen_id ); |
| 2087 | } |
| 2088 | |
| 2089 | $response = apply_filters( 'heartbeat_send', $response, $screen_id ); |
| 2090 | |
| 2091 | // Allow the transport to be replaced with long-polling easily |
| 2092 | do_action( 'heartbeat_tick', $response, $screen_id ); |
| 2093 | |
| 2094 | // Send the current time according to the server |
| 2095 | $response['server_time'] = time(); |
| 2096 | |
| 2097 | wp_send_json($response); |
| 2098 | } |