wppaste
WordPress

set_post_type( int $post_id = 0, string $post_type = 'post' ): int|false

Since
2.5.0
Source
wp-includes/post.php:2422
Updates the post type for the post ID.

Description

The page or post cache will be cleaned for the post ID.

Compatibility

WordPress
since 2.5.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

$post_idintoptional
Post ID to change post type. Default 0.Default: 0
$post_typestringoptional
Post type. Accepts 'post' or 'page' to name a few. Default 'post'.Default: 'post'

Return value

int|false
Amount of rows changed. Should be 1 for success and 0 for failure.

Performance profile

How much work a call to set_post_type() 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
24

Executed per call on PHP 8.5. The body compiles to 24.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
0

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

What it touches

  • hookthird-party callbacksapply_filters()one call below set_post_type()
  • querycontent queryget_post()one call below set_post_type()
  • cacheobject cachewp_cache_delete()one call below set_post_type()

Further down the call graph this can also reach option, 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 set_post_type() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always24sanitize_post_field(), ID(), clean_post_cache()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 24 instructions, 24 executed per call, 0 branches. The work does not change between versions.

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

Source code

View on Trac View on GitHub 

function set_post_type( $post_id = 0, $post_type = 'post' ) {	global $wpdb; 	$post_type = sanitize_post_field( 'post_type', $post_type, $post_id, 'db' );	$return    = $wpdb->update( $wpdb->posts, array( 'post_type' => $post_type ), array( 'ID' => $post_id ) ); 	clean_post_cache( $post_id ); 	return $return;}

Changelog

Introduced in 2.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 7.1.0 tag, from src/wp-includes/post.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.