WP_Theme_JSON::should_override_preset( array $theme_json, array $path, bool|array $override ): bool

Compatibility

Deprecated in WordPress 6.0.0. Use {@see 'get_metadata_boolean'} instead.

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

Parameters

$theme_jsonarray

The theme.json like structure to inspect.

$patharray

Path to inspect.

$overridebool|array

Data to compute whether to override the preset.

Return value

bool

Performance profile

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

Trivial

Touches nothing outside its own arguments.

Scaling

Constant

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

Instructions

11–36

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

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 callbacksdo_action()one call below WP_Theme_JSON::should_override_preset()

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

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

Uses · 2

• _deprecated_function()Marks a function as deprecated and inform when it has been used.
• _wp_array_get()Accesses an array in depth based on a path of keys.

Source code

View on Trac ↗View on GitHub ↗

3334	protected static function should_override_preset( $theme_json, $path, $override ) {3335		_deprecated_function( __METHOD__, '6.0.0', 'get_metadata_boolean' );3336 3337		if ( is_bool( $override ) ) {3338			return $override;3339		}3340 3341		/*3342		 * The relationship between whether to override the defaults3343		 * and whether the defaults are enabled is inverse:3344		 *3345		 * - If defaults are enabled  => theme presets should not be overridden3346		 * - If defaults are disabled => theme presets should be overridden3347		 *3348		 * For example, a theme sets defaultPalette to false,3349		 * making the default palette hidden from the user.3350		 * In that case, we want all the theme presets to be present,3351		 * so they should override the defaults.3352		 */3353		if ( is_array( $override ) ) {3354			$value = _wp_array_get( $theme_json, array_merge( $path, $override ) );3355			if ( isset( $value ) ) {3356				return ! $value;3357			}3358 3359			// Search the top-level key if none was found for this node.3360			$value = _wp_array_get( $theme_json, array_merge( array( 'settings' ), $override ) );3361			if ( isset( $value ) ) {3362				return ! $value;3363			}3364 3365			return true;3366		}3367	}

Changelog

Introduced in 5.9.0. One change between 6.7.7 and 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/class-wp-theme-json.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.