WP_Sitemaps_Taxonomies::get_taxonomies_query_args( string $taxonomy ): array
- Since
- 5.5.0
- Source
wp-includes/sitemaps/providers/class-wp-sitemaps-taxonomies.php:185
Compatibility
- WordPress
- since 5.5.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
$taxonomystring- Taxonomy name.
Return value
array- Array of WP_Term_Query arguments.
Performance profile
How much work a call to WP_Sitemaps_Taxonomies::get_taxonomies_query_args() 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
- Scaling
- Constant
- Instructions
- 19
- Plugin surface
- 1 hook
- Called by
- 2
Touches nothing outside its own arguments.
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 19.
Third-party callbacks on 'wp_sitemaps_taxonomies_query_args' run inside this call, and their cost is not bounded by anything here.
2 places in core call this, so the cost is paid more often than your own code shows.
What it touches
- hookthird-party callbacks
apply_filters()called directly
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_Sitemaps_Taxonomies::get_taxonomies_query_args() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 19 | wp_sitemaps_get_max_urls(), taxonomy() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 19 instructions, 19 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.
Hooks and filters fired · 1
One hook fires while WP_Sitemaps_Taxonomies::get_taxonomies_query_args() runs, in this order:
- apply_filters( wp_sitemaps_taxonomies_query_args )filterline 198 (+13 into the body)
Filters the taxonomy terms query arguments.
Uses · 2
- apply_filters()Calls the callback functions that have been added to a filter hook.
- wp_sitemaps_get_max_urls()Gets the maximum number of URLs for a sitemap.
Used by · 2
- WP_Sitemaps_Taxonomies::get_max_num_pages()Gets the max number of pages available for the object type.
- WP_Sitemaps_Taxonomies::get_url_list()Gets a URL list for a taxonomy sitemap.
Source code
protected function get_taxonomies_query_args( $taxonomy ) { /** * Filters the taxonomy terms query arguments. * * Allows modification of the taxonomy query arguments before querying. * * @see WP_Term_Query for a full list of arguments * * @since 5.5.0 * * @param array $args Array of WP_Term_Query arguments. * @param string $taxonomy Taxonomy name. */ $args = apply_filters( 'wp_sitemaps_taxonomies_query_args', array( 'taxonomy' => $taxonomy, 'orderby' => 'term_order', 'number' => wp_sitemaps_get_max_urls( $this->object_type ), 'hide_empty' => true, 'hierarchical' => false, 'update_term_meta_cache' => false, ), $taxonomy ); return $args; }Changelog
Introduced in 5.5.0. Unchanged from 6.7.7 through 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/sitemaps/providers/class-wp-sitemaps-taxonomies.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.