wppaste
WordPress

WP_Customize_Nav_Menus_Panel::content_template()

Since
4.3.0
Source
wp-includes/customize/class-wp-customize-nav-menus-panel.php:68
An Underscore (JS) template for this panel's content (but not its container).

Description

Class variables for this panel class are available in the data JS object; export custom variables by overriding WP_Customize_Panel::json().

Compatibility

WordPress
since 4.3.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.

Performance profile

How much work a call to WP_Customize_Nav_Menus_Panel::content_template() 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
29

Executed per call on PHP 8.5. The body compiles to 29.

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 one call costs · 1 distinct outcome

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

WhenInstructionsCalls it makes
always29_e(), __(), printf(), _e(), _e(), ->render_screen_options(), _e()

Across PHP versions

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

	protected function content_template() {		?>		<li class="panel-meta customize-info accordion-section <# if ( ! data.description ) { #> cannot-expand<# } #>">			<button type="button" class="customize-panel-back" tabindex="-1">				<span class="screen-reader-text">					<?php					/* translators: Hidden accessibility text. */					_e( 'Back' );					?>				</span>			</button>			<div class="accordion-section-title">				<span class="preview-notice">					<?php					/* translators: %s: The site/panel title in the Customizer. */					printf( __( 'You are customizing %s' ), '<strong class="panel-title">{{ data.title }}</strong>' );					?>				</span>				<button type="button" class="customize-help-toggle dashicons dashicons-editor-help" aria-expanded="false">					<span class="screen-reader-text">						<?php						/* translators: Hidden accessibility text. */						_e( 'Help' );						?>					</span>				</button>				<button type="button" class="customize-screen-options-toggle" aria-expanded="false">					<span class="screen-reader-text">						<?php						/* translators: Hidden accessibility text. */						_e( 'Menu Options' );						?>					</span>				</button>			</div>			<# if ( data.description ) { #>			<div class="description customize-panel-description">{{{ data.description }}}</div>			<# } #>			<div id="screen-options-wrap">				<?php $this->render_screen_options(); ?>			</div>		</li>		<?php		// NOTE: The following is a workaround for an inability to treat (and thus label) a list of sections as a whole.		?>		<li class="customize-control-title customize-section-title-nav_menus-heading"><?php _e( 'Menus' ); ?></li>		<?php	}

Changelog

Introduced in 4.3.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/customize/class-wp-customize-nav-menus-panel.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.