如何修改WordPress中WCMP商家注册表单的密码字段验证规则

Got it, tweaking the password rules for WCMP's vendor registration form is straightforward with WordPress hooks—never edit core WCMP or WordPress files (updates will wipe your changes). Here are two solid approaches, depending on how specific you need the rules to be:

1. Use WCMP's Dedicated Registration Validation Hook #

WCMP has a built-in hook wcmp_vendor_registration_validation made exactly for adding custom checks to vendor registration fields. This is the most targeted method since it only affects vendor signups.

Drop this code into your theme's functions.php file, or better yet, a custom plugin (so you can carry it over if you switch themes):

add_action('wcmp_vendor_registration_validation', 'custom_wcmp_vendor_password_checks');

function custom_wcmp_vendor_password_checks($errors) {
    // Grab the submitted password and confirmation from the form
    $password = isset($_POST['user_pass']) ? sanitize_text_field($_POST['user_pass']) : '';
    $confirm_pass = isset($_POST['user_pass_confirm']) ? sanitize_text_field($_POST['user_pass_confirm']) : '';

    // Rule 1: Password must be at least 10 characters
    if (strlen($password) < 10) {
        $errors->add('password_short', __('Whoops! Your password needs to be at least 10 characters long.', 'your-text-domain'));
    }

    // Rule 2: Require uppercase, lowercase, and a number
    if (!preg_match('/^(?=.*[a-z])(?=.*[A-Z])(?=.*\d).+$/', $password)) {
        $errors->add('password_complex', __('Heads up! Your password needs at least one uppercase letter, one lowercase letter, and one number.', 'your-text-domain'));
    }

    // Rule 3: Ensure password and confirmation match (WCMP might do this, but better safe than sorry)
    if ($password !== $confirm_pass) {
        $errors->add('password_mismatch', __('Oops! Your password confirmation doesn\'t match.', 'your-text-domain'));
    }

    return $errors;
}

Quick Notes: #

• Swap your-text-domain with your theme/plugin's text domain if you use translations.
• Adjust the regex to add special character requirements if needed—just add (?=.*[!@#$%^&*()_+\-=\[\]{};':"\\|,.<>\/?]) to the pattern.
• The $errors object is passed by reference in newer WCMP versions, but returning it works across all recent versions for compatibility.

2. Global Password Validation (With WCMP Targeting) #

If you want the same rules to apply to both vendors and regular users, but still need to make sure vendors follow them, you can use WordPress' global registration_errors hook. We'll add a check to only enforce the rules when it's a WCMP vendor signup:

add_filter('registration_errors', 'custom_wcmp_global_password_rules', 10, 3);

function custom_wcmp_global_password_rules($errors, $sanitized_login, $user_email) {
    // Check if this is a WCMP vendor registration (WCMP adds this POST flag)
    if (isset($_POST['wcmp_registration']) && $_POST['wcmp_registration'] === 'vendor') {
        $password = isset($_POST['user_pass']) ? sanitize_text_field($_POST['user_pass']) : '';
        
        // Add your custom rules here (copy from the first method if needed)
        if (strlen($password) < 10) {
            $errors->add('password_short', __('Vendor passwords need to be at least 10 characters long.', 'your-text-domain'));
        }
    }
    return $errors;
}

How to Test It: #

• Head to your WCMP vendor registration page.
• Try submitting a password that breaks your rules—you should see your custom error messages show up right below the password field.
• Test all edge cases: short passwords, missing required characters, mismatched confirmations, etc.

Pro Tip: #

If you're using a custom registration template or page builder, double-check the password field names. WCMP uses user_pass and user_pass_confirm by default, but some custom setups might change these. Just inspect the form HTML to confirm the name attributes.

内容的提问来源于stack exchange，提问作者Bhanuka Wijesinghe