WP_Sitemaps::redirect_sitemapxml( bool $bypass, WP_Query $query ): bool
- Since
- 5.5.0
- Source
wp-includes/sitemaps/class-wp-sitemaps.php:231
Compatibility
Deprecated in WordPress 6.7.0. Deprecated in favor of {@see WP_Rewrite::rewrite_rules()}
- 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
$bypassbool- Pass-through of the pre_handle_404 filter value.
$queryWP_Query- The WP_Query object.
Return value
bool- Bypass value.
Performance profile
How much work a call to WP_Sitemaps::redirect_sitemapxml() 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
- 8–26
- Plugin surface
- None
- Called by
- 0
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, depending on the branch taken. The body compiles to 27.
Nothing here hands control to plugin code.
Nothing in core calls this; the cost is only what you spend yourself.
What it touches
- hookthird-party callbacks
do_action()one call below WP_Sitemaps::redirect_sitemapxml()
Further down the call graph this can also reach option, cache, 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 · 4 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Sitemaps::redirect_sitemapxml() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 8 | _deprecated_function() |
| always | 18 | _deprecated_function(), ->get(), ->get() |
| always | 21 | _deprecated_function(), ->get(), ->get_index_url(), wp_safe_redirect(), exit() |
| always | 26 | _deprecated_function(), ->get(), ->get(), ->get_index_url(), wp_safe_redirect(), exit() |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 27 | 8–26 | 3 | |
| 8.5 | 27 | 8–26 | 3 | |
| 8.4 | 27 | 8–26 | 3 | 1 more instruction than PHP 8.3 |
| 8.3 | 26 | 8–24 | 3 | |
| 8.2 | 26 | 8–24 | 3 | |
| 8.1 | 26 | 8–24 | 3 | |
| 7.4 | 26 | 8–24 | 3 |
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
- _deprecated_function()Marks a function as deprecated and inform when it has been used.
- wp_safe_redirect()Performs a safe (local) redirect, using wp_redirect().
Source code
public function redirect_sitemapxml( $bypass, $query ) { _deprecated_function( __FUNCTION__, '6.7.0' ); // If a plugin has already utilized the pre_handle_404 function, return without action to avoid conflicts. if ( $bypass ) { return $bypass; } // 'pagename' is for most permalink types, name is for when the %postname% is used as a top-level field. if ( 'sitemap-xml' === $query->get( 'pagename' ) || 'sitemap-xml' === $query->get( 'name' ) ) { wp_safe_redirect( $this->index->get_index_url() ); exit(); } return $bypass; }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.7.7 tag, from
src/wp-includes/sitemaps/class-wp-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.