I worked it out. add_action( ‘user_profile_update_errors’, ‘validate_steamid_field’ ); function validate_steamid_field(&$errors, $update = null, &$user = null) { if (!preg_match(“/^STEAM_[0-5]:[01]:\d+$/”, $_POST[‘_bbp_steamid’])) { $errors->add(’empty_steamid’, “<strong>ERROR</strong>: Please Enter a valid SteamID”); } }
This appears to be a few days to a week, as said in the comments. I can say I’ve experienced the same amount of time a few times now. However, this is no rule.
register_setting – validation callback weirdness
It’s because you have typos in your code : in the function called header_logo_validate() it should be : return $new_input; EDIT: add_action( ‘admin_menu’, ‘ec1_admin’, 10, 0 ); args are useless just write add_action( ‘admin_menu’, ‘ec1_admin’); EDIT 2 : This is not a correct way to add several fields. You should put this into arrays or … Read more
Here is how I would do it: function save_extra_user_profile_fields( $user_id ) { if (!isset($_POST[‘address’]) || empty($_POST[‘address’])) { // this field was not set or was empty // do your action wp_redirect( home_url() ); // or profile page exit; } else { // field was set and contains a value // do your action update_user_meta( $user_id, … Read more
So here’s what I ended up doing: I hide the publish button, replace it with my own publish button (one that does not submit the form) and when you click that button the validation script is executed. When there are no errors, a click event is registered on the original publish button. That way, no … Read more
The default login form is not very developer friendly (and it is more developer friendly now than it used to be). If you browse the source for that page you should be able to convince yourself of that. Your plugin is not going to be able to manipulate the page the way you hope. A … Read more
Hope I did get it right: <?php function specialValidation($value) { $explode = explode(‘ ‘, $value); if(sizeof($explode) > 1) { echo ‘ERROR: You have input more than one word.’; return; } $mustBeS = substr($explode[0],0,1); if($mustBeS != ‘s’ && $mustBeS != ‘S’) { echo ‘ERROR: Your word must start with an “s” or “S”.’; return; } }
You would want to use the user_register and edit_user_profile_update actions. In this way you’ll take care of both scenarios. Be careful. Both of these fire after the user information has already made it to the database.
Remove WordPress default registration client side validation?