twentyeleven_get_theme_options(): array<string,
- Since
- Twenty Eleven 1.0
- Source
wp-content/themes/twentyeleven/inc/theme-options.php:277
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.
Return value
array<string,- string> The theme options array.
Performance profile
How much work a call to twentyeleven_get_theme_options() 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
- Scaling
- Constant
- Instructions
- 7
- Plugin surface
- None
- Called by
- 9
Reads stored settings via get_option(), cached per request but not free on a cold cache.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5. The body compiles to 7.
Nothing here hands control to plugin code.
9 places in core call this, so the cost is paid more often than your own code shows.
What it touches
- optionoption read or write
get_option()called directly - hookthird-party callbacks
apply_filters()one call below twentyeleven_get_theme_options() - cacheobject cache
wp_cache_get()one call below twentyeleven_get_theme_options() - serializeserialisation
maybe_unserialize()one call below twentyeleven_get_theme_options()
Further down the call graph this can also reach 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 · 1 distinct outcome
One number would be a lie: the work depends on which branch runs. These are every distinct cost twentyeleven_get_theme_options() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 7 | twentyeleven_get_default_theme_options(), get_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: 7 instructions, 7 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 · 2
- get_option()Retrieves an option value based on an option name.
- twentyeleven_get_default_theme_options()Returns the default options for Twenty Eleven.
Used by · 9
- twentyeleven_customize_register()Implements Twenty Eleven theme options into Customizer.
- twentyeleven_enqueue_color_scheme()Enqueues the styles for the current color scheme.
- twentyeleven_get_default_link_color()Returns the default link color for Twenty Eleven, based on color scheme.
- twentyeleven_layout_classes()Adds Twenty Eleven layout classes to the array of body classes.
- twentyeleven_print_link_color_style()Adds a style block to the theme for the current link color.
- twentyeleven_settings_field_color_scheme()Renders the Color Scheme setting field.
- twentyeleven_settings_field_layout()Renders the Layout setting field.
- twentyeleven_settings_field_link_color()Renders the Link Color setting field.
- twentyeleven_setup()Sets up theme defaults and registers support for various WordPress features.
Source code
function twentyeleven_get_theme_options() { return get_option( 'twentyeleven_theme_options', twentyeleven_get_default_theme_options() );}Changelog
Introduced in Twenty Eleven 1.0. One change between 6.7.7 and 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
none to array<string,.verified against sourceAbout this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-content/themes/twentyeleven/inc/theme-options.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.