wp_ajax_wp_privacy_erase_personal_data()

Compatibility

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Performance profile

How much work a call to wp_ajax_wp_privacy_erase_personal_data() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class

Heavy

Reaches the database via get_post().

Scaling

Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions

79–260

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 320.

Plugin surface

2 hooks

Third-party callbacks on 'wp_privacy_personal_data_erasers', 'wp_privacy_personal_data_erasure_page' run inside this call, and their cost is not bounded by anything here.

Called by

0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

• hookthird-party callbacksapply_filters()called directly
• querycontent queryget_post()one call below wp_ajax_wp_privacy_erase_personal_data()

Further down the call graph this can also reach option, cache, serialize and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 332 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_ajax_wp_privacy_erase_personal_data() can have, taken from its control-flow graph on PHP 8.5.

This body has more branch combinations than are worth enumerating, so the table covers the outcomes found first rather than every one that exists.

Hooks and filters fired · 2

2 hooks fire while wp_ajax_wp_privacy_erase_personal_data() runs, in this order:

1. 1
   apply_filters( wp_privacy_personal_data_erasers )filterline 5182 (+64 into the body)

   Filters the array of personal data eraser callbacks.

2. 2
   apply_filters( wp_privacy_personal_data_erasure_page )filterline 5340 (+222 into the body)

   Filters a page of personal data eraser data.

Uses · 10

• wp_send_json_error()Sends a JSON response back to an Ajax request, indicating failure.
• __()Retrieves the translation of $text.
• current_user_can()Returns whether the current user has the specified capability.
• check_ajax_referer()Verifies the Ajax request to prevent processing requests external of the blog.
• wp_get_user_request()Returns the user request object for the specified request ID.
• is_email()Verifies that an email is valid.
• apply_filters()Calls the callback functions that have been added to a filter hook.
• esc_html()Escaping for HTML blocks.
• is_wp_error()Checks whether the given variable is a WordPress Error.
• wp_send_json_success()Sends a JSON response back to an Ajax request, indicating success.

Source code

View on Trac ↗View on GitHub ↗

5118function wp_ajax_wp_privacy_erase_personal_data() {5119 5120	if ( empty( $_POST['id'] ) ) {5121		wp_send_json_error( __( 'Missing request ID.' ) );5122	}5123 5124	$request_id = (int) $_POST['id'];5125 5126	if ( $request_id < 1 ) {5127		wp_send_json_error( __( 'Invalid request ID.' ) );5128	}5129 5130	// Both capabilities are required to avoid confusion, see `_wp_personal_data_removal_page()`.5131	if ( ! current_user_can( 'erase_others_personal_data' ) || ! current_user_can( 'delete_users' ) ) {5132		wp_send_json_error( __( 'Sorry, you are not allowed to perform this action.' ) );5133	}5134 5135	check_ajax_referer( 'wp-privacy-erase-personal-data-' . $request_id, 'security' );5136 5137	// Get the request.5138	$request = wp_get_user_request( $request_id );5139 5140	if ( ! $request || 'remove_personal_data' !== $request->action_name ) {5141		wp_send_json_error( __( 'Invalid request type.' ) );5142	}5143 5144	$email_address = $request->email;5145 5146	if ( ! is_email( $email_address ) ) {5147		wp_send_json_error( __( 'Invalid email address in request.' ) );5148	}5149 5150	if ( ! isset( $_POST['eraser'] ) ) {5151		wp_send_json_error( __( 'Missing eraser index.' ) );5152	}5153 5154	$eraser_index = (int) $_POST['eraser'];5155 5156	if ( ! isset( $_POST['page'] ) ) {5157		wp_send_json_error( __( 'Missing page index.' ) );5158	}5159 5160	$page = (int) $_POST['page'];5161 5162	/**5163	 * Filters the array of personal data eraser callbacks.5164	 *5165	 * @since 4.9.65166	 *5167	 * @param array $args {5168	 *     An array of callable erasers of personal data. Default empty array.5169	 *5170	 *     @type array ...$0 {5171	 *         Array of personal data exporters.5172	 *5173	 *         @type callable $callback               Callable eraser that accepts an email address and a page5174	 *                                                number, and returns an array with boolean values for5175	 *                                                whether items were removed or retained and any messages5176	 *                                                from the eraser, as well as if additional pages are5177	 *                                                available.5178	 *         @type string   $exporter_friendly_name Translated user facing friendly name for the eraser.5179	 *     }5180	 * }5181	 */5182	$erasers = apply_filters( 'wp_privacy_personal_data_erasers', array() );5183 5184	// Do we have any registered erasers?5185	if ( 0 < count( $erasers ) ) {5186 5187		if ( $eraser_index < 1 ) {5188			wp_send_json_error( __( 'Eraser index cannot be less than one.' ) );5189		}5190 5191		if ( $eraser_index > count( $erasers ) ) {5192			wp_send_json_error( __( 'Eraser index is out of range.' ) );5193		}5194 5195		if ( $page < 1 ) {5196			wp_send_json_error( __( 'Page index cannot be less than one.' ) );5197		}

Changelog

Introduced in 4.9.6. Unchanged from 6.7.7 through 7.1.0.

1. 6.7.7
2. 6.8.8
3. 6.9.7
4. 7.0.4
5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data

Generated from the wordpress-develop 6.9.7 tag, from src/wp-admin/includes/ajax-actions.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.

Corrections

Something wrong on this page? Report it and it gets fixed in the next regeneration.