wppaste
WordPress

Featured_Content::validate_settings( array $input ): array

Since
Twenty Fourteen 1.0
Source
wp-content/themes/twentyfourteen/inc/featured-content.php:489
Validates featured content settings.

Description

Makes sure that all user supplied content is in an expected format before saving to the database. This function will also delete the transient set in Featured_Content::get_featured_content().

Compatibility

WordPress
since Twenty Fourteen 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 every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$inputarray
Array of settings input.

Return value

array
Validated settings output.

Performance profile

How much work a call to Featured_Content::validate_settings() 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_term().

Scaling
Constant

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

Instructions
14–42

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
1

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

What it touches

  • querycontent queryget_term()one call below Featured_Content::validate_settings()
  • hookthird-party callbacksdo_action()one call below Featured_Content::validate_settings()

Further down the call graph this can also reach 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 Featured_Content::validate_settings() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
empty($input)14–17::delete_transient()
!empty($input)28–31get_term_by(), ::delete_transient()
!empty($input)34–42get_term_by(), wp_create_tag(), is_wp_error(), ::delete_transient()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 49 instructions, 14–42 executed per call, 6 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 · 4

Used by · 1

Source code

View on Trac View on GitHub 

	public static function validate_settings( $input ) {		$output = array(); 		if ( empty( $input['tag-name'] ) ) {			$output['tag-id'] = 0;		} else {			$term = get_term_by( 'name', $input['tag-name'], 'post_tag' ); 			if ( $term ) {				$output['tag-id'] = $term->term_id;			} else {				$new_tag = wp_create_tag( $input['tag-name'] ); 				if ( ! is_wp_error( $new_tag ) && isset( $new_tag['term_id'] ) ) {					$output['tag-id'] = $new_tag['term_id'];				}			} 			$output['tag-name'] = $input['tag-name'];		} 		$output['hide-tag'] = isset( $input['hide-tag'] ) && $input['hide-tag'] ? 1 : 0; 		// Delete the featured post IDs transient.		self::delete_transient(); 		return $output;	}

Changelog

Introduced in Twenty Fourteen 1.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-content/themes/twentyfourteen/inc/featured-content.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.