wp_sitemaps_get_max_urls( string $object_type ): int
- Since
- 5.5.0
- Source
wp-includes/sitemaps.php:81
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
$object_typestring- Object type for sitemap to be filtered (e.g. 'post', 'term', 'user').
Return value
int- The maximum number of URLs.
Performance profile
How much work a call to wp_sitemaps_get_max_urls() 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
- 7
- Plugin surface
- 1 hook
- Called by
- 6
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 7.
Third-party callbacks on 'wp_sitemaps_max_urls' run inside this call, and their cost is not bounded by anything here.
6 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_get_max_urls() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 7 | apply_filters() |
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.
Hooks and filters fired · 1
One hook fires while wp_sitemaps_get_max_urls() runs, in this order:
- apply_filters( wp_sitemaps_max_urls )filterline 90 (+9 into the body)
Filters the maximum number of URLs displayed on a sitemap.
Uses · 1
- apply_filters()Calls the callback functions that have been added to a filter hook.
Used by · 6
- WP_Sitemaps_Posts::get_posts_query_args()Returns the query args for retrieving posts to list in the sitemap.
- WP_Sitemaps_Taxonomies::get_max_num_pages()Gets the max number of pages available for the object type.
- WP_Sitemaps_Taxonomies::get_taxonomies_query_args()Returns the query args for retrieving taxonomy terms to list in the sitemap.
- WP_Sitemaps_Taxonomies::get_url_list()Gets a URL list for a taxonomy sitemap.
- WP_Sitemaps_Users::get_max_num_pages()Gets the max number of pages available for the object type.
- WP_Sitemaps_Users::get_users_query_args()Returns the query args for retrieving users to list in the sitemap.
Source code
function wp_sitemaps_get_max_urls( $object_type ) { /** * Filters the maximum number of URLs displayed on a sitemap. * * @since 5.5.0 * * @param int $max_urls The maximum number of URLs included in a sitemap. Default 2000. * @param string $object_type Object type for sitemap to be filtered (e.g. 'post', 'term', 'user'). */ return apply_filters( 'wp_sitemaps_max_urls', 2000, $object_type );}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.9.7 tag, from
src/wp-includes/sitemaps.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.