Source View: wp_privacy_personal_data_erasure_page

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

  • Action hooks look like this: do_action( "hook_name" )
  • Filter hooks look like this: 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.

Source View

Line Code
4819       * @since 4.9.6
4820       *
4821       * @param array  $response        The personal data for the given exporter and page.
4822       * @param int    $eraser_index    The index of the eraser that provided this data.
4823       * @param string $email_address   The email address associated with this personal data.
4824       * @param int    $page            The page for this response.
4825       * @param int    $request_id      The privacy request post ID associated with this request.
4826       * @param string $eraser_key      The key (slug) of the eraser that provided this data.
4827       */
4828      $response = apply_filters( 'wp_privacy_personal_data_erasure_page', $response, $eraser_index, $email_address, $page, $request_id, $eraser_key );
4829
4830      if ( is_wp_error( $response ) ) {
4831           wp_send_json_error( $response );
4832      }
4833
4834      wp_send_json_success( $response );
4835 }
4836