wppaste
WordPress

user_trailingslashit( string $url, string $type_of_url = '' ): string

Since
2.2.0
Source
wp-includes/link-template.php:47
Retrieves a trailing-slashed string if the site is set for adding trailing slashes.

Description

Conditionally adds a trailing slash if the permalink structure has a trailing slash, strips the trailing slash if not. The string is passed through the 'user_trailingslashit' filter. Will remove trailing slash from string, if site is not set to have them.

Compatibility

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

$urlstring
URL with or without a trailing slash.
$type_of_urlstringoptional
The type of URL being considered (e.g. single, category, etc) for use in the filter. Default empty string.Default: ''

Return value

string
The URL with the trailing slash appended or stripped.

Performance profile

How much work a call to user_trailingslashit() 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
15–16

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 20.

Plugin surface
1 hook

Third-party callbacks on 'user_trailingslashit' run inside this call, and their cost is not bounded by anything here.

Called by
29

29 places in core call this, so the cost is paid more often than your own code shows.

What it touches

  • hookthird-party callbacksapply_filters()called directly

What one call costs · 2 distinct outcomes

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

WhenInstructionsCalls it makes
!$wp_rewrite15untrailingslashit(), apply_filters()
$wp_rewrite16trailingslashit(), 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: 20 instructions, 15–16 executed per call, 1 branch. 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 user_trailingslashit() runs, in this order:

  1. apply_filters( user_trailingslashit )filterline 65 (+18 into the body)

    Filters the trailing-slashed string, depending on whether the site is set to use trailing slashes.

Uses · 3

Used by · 29

Show all 29

Source code

function user_trailingslashit( $url, $type_of_url = '' ) {	global $wp_rewrite;	if ( $wp_rewrite->use_trailing_slashes ) {		$url = trailingslashit( $url );	} else {		$url = untrailingslashit( $url );	} 	/**	 * Filters the trailing-slashed string, depending on whether the site is set to use trailing slashes.	 *	 * @since 2.2.0	 *	 * @param string $url         URL with or without a trailing slash.	 * @param string $type_of_url The type of URL being considered. Accepts 'single', 'single_trackback',	 *                            'single_feed', 'single_paged', 'commentpaged', 'paged', 'home', 'feed',	 *                            'category', 'page', 'year', 'month', 'day', 'post_type_archive'.	 */	return apply_filters( 'user_trailingslashit', $url, $type_of_url );}

Changelog

Introduced in 2.2.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 7.1.0 tag, from src/wp-includes/link-template.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.