wp_is_post_autosave( int|WP_Post $post ): int|false
- Since
- 2.6.0
- Source
wp-includes/revision.php:337
Compatibility
- WordPress
- since 2.6.0
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.
Parameters
$postint|WP_Post- Post ID or post object.
Return value
int|false- ID of autosave's parent on success, false if not a revision.
Performance profile
How much work a call to wp_is_post_autosave() 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
- Scaling
- Constant
- Instructions
- 7–14
- Plugin surface
- None
- Called by
- 7
Reaches the database via get_post().
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 16.
Nothing here hands control to plugin code.
7 places in core call this, so the cost is paid more often than your own code shows.
What it touches
- querycontent query
get_post()one call below wp_is_post_autosave()
Further down the call graph this can also reach hook, 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_is_post_autosave() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 7–14 | wp_get_post_revision() |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 16 | 7–14 | 2 | |
| 8.5 | 16 | 7–14 | 2 | |
| 8.4 | 16 | 7–14 | 2 | 3 fewer instructions than PHP 8.3 |
| 8.3 | 19 | 7–17 | 2 | |
| 8.2 | 19 | 7–17 | 2 | |
| 8.1 | 19 | 7–17 | 2 | 1 fewer instruction than PHP 7.4 |
| 7.4 | 20 | 7–18 | 2 |
An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.
Uses · 2
- wp_get_post_revision()Gets a post revision.
- str_contains()Polyfill for `str_contains()` function added in PHP 8.0.
Used by · 7
- WP_REST_Autosaves_Controller::prepare_item_for_response()Prepares the revision for the REST response.
- wp_list_post_revisions()Displays a list of a post's revisions.
- wp_post_revision_title()Retrieves formatted date timestamp of a revision (linked to that revisions's page).
- wp_post_revision_title_expanded()Retrieves formatted date timestamp of a revision (linked to that revisions's page).
- wp_prepare_revisions_for_js()Prepare revisions for JavaScript.
- wp_xmlrpc_server::wp_getRevisions()Retrieves revisions for a specific post.
- wp_xmlrpc_server::wp_restoreRevision()Restores a post revision.
Source code
function wp_is_post_autosave( $post ) { $post = wp_get_post_revision( $post ); if ( ! $post ) { return false; } if ( str_contains( $post->post_name, "{$post->post_parent}-autosave" ) ) { return (int) $post->post_parent; } return false;}Changelog
Introduced in 2.6.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 6.7.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.