wppaste
WordPress

Twenty_Eleven_Ephemera_Widget::update( array $new_instance, array $old_instance ): array<string,

Since
Twenty Eleven 1.0
Source
wp-content/themes/twentyeleven/inc/widgets.php:164
Updates widget settings.

Description

Deals with the settings when they are saved by the admin. Here is where any validation should be dealt with.

Compatibility

WordPress
since Twenty Eleven 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

$new_instancearray
New widget instance.
$old_instancearray
Original widget instance.

Return value

array<string,
string|int> Updated widget instance.

Performance profile

How much work a call to Twenty_Eleven_Ephemera_Widget::update() 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 Twenty_Eleven_Ephemera_Widget::update().

Scaling
Constant

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

Instructions
23–26

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

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

  • sqldatabase queryTwenty_Eleven_Ephemera_Widget::update()this function does it
  • cacheobject cachewp_cache_get()called directly
  • optionoption read or writedelete_option()called directly
  • hookthird-party callbacksdo_action()one call below Twenty_Eleven_Ephemera_Widget::update()

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

WhenInstructionsCalls it makes
!isset($alloptions)23strip_tags(), ->flush_widget_cache(), wp_cache_get()
isset($alloptions)26strip_tags(), ->flush_widget_cache(), wp_cache_get(), delete_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: 26 instructions, 23–26 executed per call, 1 branch. 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

	public function update( $new_instance, $old_instance ) {		$instance           = $old_instance;		$instance['title']  = strip_tags( $new_instance['title'] );		$instance['number'] = (int) $new_instance['number'];		$this->flush_widget_cache(); 		$alloptions = wp_cache_get( 'alloptions', 'options' );		if ( isset( $alloptions['widget_twentyeleven_ephemera'] ) ) {			delete_option( 'widget_twentyeleven_ephemera' );		} 		return $instance;	}

Changelog

Introduced in Twenty Eleven 1.0. 3 changes 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.

7.0.4
Parameter $new_instance retyped from untyped to array.verified against source
7.0.4
Parameter $old_instance retyped from untyped to array.verified against source
7.0.4
Return type changed from none to array<string,.verified against source
Twenty Eleven 1.0
Twenty Eleven 1.0from the docblock

About this page

Parsed data
Generated from the wordpress-develop 7.1.0 tag, from src/wp-content/themes/twentyeleven/inc/widgets.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.