_wp_post_revision_data( array|WP_Post $post = array(), bool $autosave = false ): array

Compatibility

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

Parameters

$postarray|WP_Postoptional

A post array or a WP_Post object to be processed for insertion as a post revision. Default empty array.Default: array()

$autosavebooloptional

Is the revision an autosave? Default false.Default: false

Return value

array

Post array ready to be inserted as a post revision.

Performance profile

How much work a call to _wp_post_revision_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

Scales with input

The body loops, so the work grows with what you pass in.

Instructions

44–54

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

Plugin surface

None

Nothing here hands control to plugin code.

Called by

3

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

What it touches

• querycontent queryget_post()called directly
• hookthird-party callbacksapply_filters()one call below _wp_post_revision_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 · 2 distinct outcomes

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

Uses · 2

• get_post()Retrieves post data given a post ID or post object.
• _wp_post_revision_fields()Determines which fields of posts are to be saved in revisions.

Used by · 3

• WP_REST_Autosaves_Controller::create_post_autosave()Creates autosave for the specified post.
• _wp_put_post_revision()Inserts post data into the posts table as a post revision.
• wp_create_post_autosave()Creates autosave data for the specified post from `$_POST` data.

Source code

View on Trac ↗View on GitHub ↗

75function _wp_post_revision_data( $post = array(), $autosave = false ) {76	if ( ! is_array( $post ) ) {77		$post = get_post( $post, ARRAY_A );78	}79 80	$fields = _wp_post_revision_fields( $post );81 82	$revision_data = array();83 84	foreach ( array_intersect( array_keys( $post ), array_keys( $fields ) ) as $field ) {85		$revision_data[ $field ] = $post[ $field ];86	}87 88	$revision_data['post_parent']   = $post['ID'];89	$revision_data['post_status']   = 'inherit';90	$revision_data['post_type']     = 'revision';91	$revision_data['post_name']     = $autosave ? "$post[ID]-autosave-v1" : "$post[ID]-revision-v1"; // "1" is the revisioning system version.92	$revision_data['post_date']     = isset( $post['post_modified'] ) ? $post['post_modified'] : '';93	$revision_data['post_date_gmt'] = isset( $post['post_modified_gmt'] ) ? $post['post_modified_gmt'] : '';94 95	return $revision_data;96}

Changelog

Introduced in 4.5.0. 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-includes/revision.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.