wp_maybe_update_network_site_counts( int|null $network_id = null )

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

$network_idint|nulloptional

ID of the network. Default is the current network.Default: null

Performance profile

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

Moderate

Reads stored settings via update_network_option(), cached per request but not free on a cold cache.

Scaling

Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions

13–16

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

Plugin surface

1 hook

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

Called by

1

1 place in core call this, so the cost is paid more often than your own code shows.

What it touches

• hookthird-party callbacksapply_filters()called directly
• optionnetwork optionupdate_network_option()one call below wp_maybe_update_network_site_counts()

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

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

Hooks and filters fired · 1

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

1. 1
   apply_filters( enable_live_network_counts )filterline 2512 (+13 into the body)

   Filters whether to update network site or user counts when a new site is created.

Uses · 3

• wp_is_large_network()Determines whether or not we have a large network.
• apply_filters()Calls the callback functions that have been added to a filter hook.
• wp_update_network_site_counts()Updates the network-wide site count.

Used by · 1

• wp_maybe_update_network_site_counts_on_update()Updates the count of sites for a network based on a changed site.

Source code

View on Trac ↗View on GitHub ↗

2499function wp_maybe_update_network_site_counts( $network_id = null ) {2500	$is_small_network = ! wp_is_large_network( 'sites', $network_id );2501 2502	/**2503	 * Filters whether to update network site or user counts when a new site is created.2504	 *2505	 * @since 3.7.02506	 *2507	 * @see wp_is_large_network()2508	 *2509	 * @param bool   $small_network Whether the network is considered small.2510	 * @param string $context       Context. Either 'users' or 'sites'.2511	 */2512	if ( ! apply_filters( 'enable_live_network_counts', $is_small_network, 'sites' ) ) {2513		return;2514	}2515 2516	wp_update_network_site_counts( $network_id );2517}

Changelog

Introduced in 3.7.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.8.8 tag, from src/wp-includes/ms-functions.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.