confirm_user_signup( string $user_name, string $user_email )
- Since
- MU (3.0.0)
- Source
wp-signup.php:709
Compatibility
- WordPress
- since MU (3.0.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
$user_namestring- The username.
$user_emailstring- The user's email address.
Performance profile
How much work a call to confirm_user_signup() 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
- 33
- Plugin surface
- 1 hook
- Called by
- 1
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 33.
Third-party callbacks on 'signup_finished' run inside this call, and their cost is not bounded by anything here.
1 place in core call this, so the cost is paid more often than your own code shows.
What it touches
- hookthird-party callbacks
do_action()called directly
Further down the call graph this can also reach query, option, cache, serialize 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 confirm_user_signup() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 33 | __(), printf(), _e(), __(), printf(), _e(), do_action() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 33 instructions, 33 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 confirm_user_signup() runs, in this order:
- do_action( signup_finished )actionline 727 (+18 into the body)
Fires when the site or user sign-up process is complete.
Uses · 3
- __()Retrieves the translation of $text.
- _e()Displays translated text.
- do_action()Calls the callback functions that have been added to an action hook.
Used by · 1
- validate_user_signup()Validates the new user sign-up.
Source code
function confirm_user_signup( $user_name, $user_email ) { ?> <h2> <?php /* translators: %s: Username. */ printf( __( '%s is your new username' ), $user_name ) ?> </h2> <p><?php _e( 'But, before you can start using your new username, <strong>you must activate it</strong>.' ); ?></p> <p> <?php /* translators: %s: The user email address. */ printf( __( 'Check your inbox at %s and click on the given link.' ), '<strong>' . $user_email . '</strong>' ); ?> </p> <p><?php _e( 'If you do not activate your username within two days, you will have to sign up again.' ); ?></p> <?php /** This action is documented in wp-signup.php */ do_action( 'signup_finished' );}Changelog
Introduced in MU (3.0.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 7.1.0 tag, from
src/wp-signup.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.