_wp_personal_data_cleanup_requests()

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_personal_data_cleanup_requests() 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

Scales with input

The body loops, so the work grows with how much data it finds.

Instructions

23–24

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

Plugin surface

1 hook

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

Called by

1

1 place in core call this, so the cost is paid more often than your own code shows.

What it touches

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

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 · 1 distinct outcome

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

Hooks and filters fired · 1

One hook fires while _wp_personal_data_cleanup_requests() runs, in this order:

1. 1
   apply_filters( user_request_key_expiration )filterline 197 (+2 into the body)

   Filters the expiration time of confirm keys.

Uses · 3

• apply_filters()Calls the callback functions that have been added to a filter hook.
• wp_update_post()Updates a post with new post data.
• WP_Query::__construct()Constructor.

Used by · 1

• wp_privacy_personal_data_cleanup_requests()Fires the personal data cleanup requests handler during cron.

Source code

View on Trac ↗View on GitHub ↗

195function _wp_personal_data_cleanup_requests() {196	/** This filter is documented in wp-includes/user.php */197	$expires = (int) apply_filters( 'user_request_key_expiration', DAY_IN_SECONDS );198 199	$requests_query = new WP_Query(200		array(201			'post_type'      => 'user_request',202			'posts_per_page' => -1,203			'post_status'    => 'request-pending',204			'fields'         => 'ids',205			'date_query'     => array(206				array(207					/*208					 * The local-time column must be used here, not post_modified_gmt:209					 * WP_Date_Query resolves relative date strings like "N seconds ago"210					 * in the site's timezone, so comparing against the GMT column would211					 * shift the expiry window by the site's UTC offset.212					 */213					'column' => 'post_modified',214					'before' => $expires . ' seconds ago',215				),216			),217		)218	);219 220	$request_ids = $requests_query->posts;221 222	foreach ( $request_ids as $request_id ) {223		wp_update_post(224			array(225				'ID'            => $request_id,226				'post_status'   => 'request-failed',227				'post_password' => '',228			)229		);230	}231}

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 7.1.0 tag, from src/wp-admin/includes/privacy-tools.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.