#36: heartbeat_send

The heartbeat_send allows you to modify the Heartbeat response sent when no $_POST data is passed. It is the logged-in, privileged sibling of heartbeat_nopriv_send.

It was added in 3.6.

It is evaluated in wp_ajax_heartbeat() in the wp-admin/includes/ajax-actions.php file.

Like heartbeat_nopriv_send, heartbeat_send accepts 2 arguments:

  1. array|object $response The response object or array.
  2. string $screen_id The screen id.

Example:

There is no example for this filter yet. Have an idea for one? Submit an example.

#35: heartbeat_received

The heartbeat_received ilter allows you to modify the Heartbeat response data in logged-in AJAX situations. It is the logged-in version of heartbeat_nopriv_received.

It was added in 3.6.

It is evaluated in wp_ajax_heartbeat() in the wp-admin/includes/ajax-actions.php file.

Like heartbeat_nopriv_received, heartbeat_received accepts 3 arguments:

  1. array|object $response The nopriv Heartbeat response.
  2. array $data An array of data passed via $_POST.
  3. string $screen_id The screen id.

Example:

Since we already have a working example for heartbeat_nopriv_received, we’ll reuse that here.

The following example is based on a Heartbeat example Gist written by Jason Coleman and kindly suggested by jsternberg in the comments.

It modifies the $response value to return a ‘marco polo’ scenario showing the server “responding” to the AJAX call. Thanks to for the suggestion!

View the code example on Gist.

#31: wp_check_post_lock_window

The wp_check_post_lock_window filter allows you to modify the post lock window duration.

It is evaluated in:

wp_check_post_lock_window accepts a single argument:

  1. int $interval The interval in seconds the post lock window should last. Default is 120.

Example:

The following example extends the post lock window to 2.5 minutes, or 150 seconds.

View the code example on Gist.