_publish_post_hook( int $post_id )

Description

Compatibility

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

Parameters

$post_idint

The ID of the post being published.

Performance profile

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

6–47

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

Plugin surface

1 hook

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

Called by

0

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

What it touches

• hookthird-party callbacksdo_action()called directly
• optionoption read or writeget_option()called directly
• cacheobject cachewp_cache_get()one call below _publish_post_hook()
• serializeserialisationmaybe_unserialize()one call below _publish_post_hook()
• querycontent queryget_post()one call below _publish_post_hook()

Further down the call graph this can also reach transient. That is the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 18 distinct outcomes

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

Hooks and filters fired · 1

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

1. 1
   do_action( xmlrpc_publish_post )actionline 8229 (+9 into the body)

   Fires when _publish_post_hook() is called during an XML-RPC request.

Uses · 6

• do_action()Calls the callback functions that have been added to an action hook.
• get_option()Retrieves an option value based on an option name.
• add_post_meta()Adds a meta field to the given post.
• get_to_ping()Retrieves URLs that need to be pinged.
• wp_next_scheduled()Retrieves the timestamp of the next scheduled event for the given hook.
• wp_schedule_single_event()Schedules an event to run only once.

Source code

View on Trac ↗View on GitHub ↗

8220function _publish_post_hook( $post_id ) {8221	if ( defined( 'XMLRPC_REQUEST' ) ) {8222		/**8223		 * Fires when _publish_post_hook() is called during an XML-RPC request.8224		 *8225		 * @since 2.1.08226		 *8227		 * @param int $post_id Post ID.8228		 */8229		do_action( 'xmlrpc_publish_post', $post_id );8230	}8231 8232	if ( defined( 'WP_IMPORTING' ) ) {8233		return;8234	}8235 8236	if ( get_option( 'default_pingback_flag' ) ) {8237		add_post_meta( $post_id, '_pingme', '1', true );8238	}8239	add_post_meta( $post_id, '_encloseme', '1', true );8240 8241	$to_ping = get_to_ping( $post_id );8242	if ( ! empty( $to_ping ) ) {8243		add_post_meta( $post_id, '_trackbackme', '1' );8244	}8245 8246	if ( ! wp_next_scheduled( 'do_pings' ) ) {8247		wp_schedule_single_event( time(), 'do_pings' );8248	}8249}

Changelog

Introduced in 2.3.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.