wppaste
WordPress

wp_trash_post( int $post_id = 0 ): WP_Post|false|null

Since
2.9.0
Source
wp-includes/post.php:3884
Moves a post or page to the Trash

Description

If Trash is disabled, the post or page is permanently deleted.

Compatibility

WordPress
since 2.9.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. Default is the ID of the global $post if EMPTY_TRASH_DAYS equals true.Default: 0

Return value

WP_Post|false|null
Post data on success, false or null on failure.

Performance profile

How much work a call to wp_trash_post() 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
8–54

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

Plugin surface
3 hooks

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

Called by
7

7 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()called directly

Further down the call graph this can also reach cache, serialize, option 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 · 5 distinct outcomes

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

WhenInstructionsCalls it makes
always8wp_delete_post()
always9–12get_post()
$check !== null22get_post(), apply_filters()
$check === null46get_post(), apply_filters(), do_action(), add_post_meta(), time(), add_post_meta(), ID()
$check === null54get_post(), apply_filters(), do_action(), add_post_meta(), time(), add_post_meta(), ID(), wp_trash_post_comments(), do_action()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 63 instructions, 8–54 executed per call, 5 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.

Hooks and filters fired · 3

3 hooks fire while wp_trash_post() runs, in this order:

  1. apply_filters( pre_trash_post )filterline 3911 (+27 into the body)

    Filters whether a post trashing should take place.

  2. do_action( wp_trash_post )actionline 3926 (+42 into the body)

    Fires before a post is sent to the Trash.

  3. do_action( trashed_post )actionline 3953 (+69 into the body)

    Fires after a post is sent to the Trash.

Uses · 7

Used by · 7

Source code

function wp_trash_post( $post_id = 0 ) {	if ( ! EMPTY_TRASH_DAYS ) {		return wp_delete_post( $post_id, true );	} 	$post = get_post( $post_id ); 	if ( ! $post ) {		return $post;	} 	if ( 'trash' === $post->post_status ) {		return false;	} 	$previous_status = $post->post_status; 	/**	 * Filters whether a post trashing should take place.	 *	 * @since 4.9.0	 * @since 6.3.0 Added the `$previous_status` parameter.	 *	 * @param bool|null $trash           Whether to go forward with trashing.	 * @param WP_Post   $post            Post object.	 * @param string    $previous_status The status of the post about to be trashed.	 */	$check = apply_filters( 'pre_trash_post', null, $post, $previous_status ); 	if ( null !== $check ) {		return $check;	} 	/**	 * Fires before a post is sent to the Trash.	 *	 * @since 3.3.0	 * @since 6.3.0 Added the `$previous_status` parameter.	 *	 * @param int    $post_id         Post ID.	 * @param string $previous_status The status of the post about to be trashed.	 */	do_action( 'wp_trash_post', $post_id, $previous_status ); 	add_post_meta( $post_id, '_wp_trash_meta_status', $previous_status );	add_post_meta( $post_id, '_wp_trash_meta_time', time() ); 	$post_updated = wp_update_post(		array(			'ID'          => $post_id,			'post_status' => 'trash',		)	); 	if ( ! $post_updated ) {		return false;	} 	wp_trash_post_comments( $post_id ); 	/**	 * Fires after a post is sent to the Trash.	 *	 * @since 2.9.0	 * @since 6.3.0 Added the `$previous_status` parameter.	 *	 * @param int    $post_id         Post ID.	 * @param string $previous_status The status of the post at the point where it was trashed.	 */	do_action( 'trashed_post', $post_id, $previous_status ); 	return $post;}

Changelog

Introduced in 2.9.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.7.7 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.