validate_user_signup(): bool
- Since
- MU (3.0.0)
- Source
wp-signup.php:678
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.
Return value
bool- True if new user sign-up was validated, false on error.
Performance profile
How much work a call to validate_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
- 15–27
- Plugin surface
- 1 hook
- 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 38.
Third-party callbacks on 'add_signup_meta' run inside this call, and their cost is not bounded by anything here.
Nothing in core calls this; the cost is only what you spend yourself.
What it touches
- hookthird-party callbacks
apply_filters()called directly
Further down the call graph this can also reach option, transient, query, cache, serialize and http. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.
What one call costs · 3 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost validate_user_signup() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
->has_errors() | 15 | validate_user_form(), ->has_errors(), signup_user() |
!->has_errors() | 18 | validate_user_form(), ->has_errors(), signup_blog() |
!->has_errors() | 27 | validate_user_form(), ->has_errors(), apply_filters(), wpmu_signup_user(), confirm_user_signup() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 38 instructions, 15–27 executed per call, 2 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 validate_user_signup() runs, in this order:
- apply_filters( add_signup_meta )filterline 695 (+17 into the body)
Filters the new default site meta variables.
Uses · 6
- validate_user_form()Validates user sign-up name and email.
- signup_user()Shows a form for a visitor to sign up for a new user account.
- signup_blog()Shows a form for a user or visitor to sign up for a new site.
- wpmu_signup_user()Records user signup information for future activation.
- apply_filters()Calls the callback functions that have been added to a filter hook.
- confirm_user_signup()Shows a message confirming that the new user has been registered and is awaiting activation.
Source code
function validate_user_signup() { $result = validate_user_form(); $user_name = $result['user_name']; $user_email = $result['user_email']; $errors = $result['errors']; if ( $errors->has_errors() ) { signup_user( $user_name, $user_email, $errors ); return false; } if ( 'blog' === $_POST['signup_for'] ) { signup_blog( $user_name, $user_email ); return false; } /** This filter is documented in wp-signup.php */ wpmu_signup_user( $user_name, $user_email, apply_filters( 'add_signup_meta', array() ) ); confirm_user_signup( $user_name, $user_email ); return true;}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.