wppaste
WordPress

_reset_privacy_policy_page_for_post( int $post_id )

Since
7.1.0
Source
wp-includes/post.php:4065
Resets the Privacy Policy page ID option when the Privacy Policy page is permanently deleted, to prevent uncached database queries for a non-existent page.

Compatibility

WordPress
since 7.1.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in 1 of the 5 tracked releases, added in 7.1.0, and compiles on PHP 7.4 through 8.6-dev.

Parameters

$post_idint
The ID of the post being deleted.

Performance profile

How much work a call to _reset_privacy_policy_page_for_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
7–17

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

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

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

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 · 3 distinct outcomes

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

WhenInstructionsCalls it makes
always7get_post_type()
$post_id !== false13get_post_type(), get_option()
$post_id === false17get_post_type(), get_option(), update_option()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 17 instructions, 7–17 executed per call, 2 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 · 3

Source code

View on Trac View on GitHub 

function _reset_privacy_policy_page_for_post( int $post_id ): void {	if ( 'page' === get_post_type( $post_id ) && ( (int) get_option( 'wp_page_for_privacy_policy' ) === $post_id ) ) {		update_option( 'wp_page_for_privacy_policy', 0 );	}}

Changelog

Introduced in 7.1.0.

Signature, return type and hooks compared across 1 parsed release.

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.