Editing the Registration Confirmation Notice on Registration Form

It’s not a one liner code solution. It’s the important part of a callback function hooked to “wp_login_errors”. Since you already wrote a filter callback I thought you knew what to do with it. Bad assumption, my apologies.

function my_reg_message( $error ) {
    $error->add('registered', __('Log in info sent to XXX'), 'message');
    return $error;
}
add_filter( 'wp_login_errors', 'my_reg_message' );

I’m not sure what you had in mind for ‘XXX’. There’s scant data to work with when this filter fires.

If you’re going to edit wp_login.php directly, just alter the existing message and be done with it. There’d be no point in fussing with hooks. But that is a really bad approach, please don’t even consider this.

First, please restore wp-login.php to it’s default state. Maybe I’m a little slow to connect the dots, but I now think I see where you’re going with this. You are setting up your site to manage registration via SMS instead of email, yes? Great idea! Have you searched for an existing plugin that does this? Why reinvent the wheel?

My next question was going to be where are you placing your custom code? But if you’ve found no plugin that does this, you’ve got to do this as your own plugin. People are going to want this! See Writing a Plugin. The basic setup is really simple. Include the code from my previous post on the plugin code page. That will alter the confirmation message.

Edit: I just saw your post regarding creation of plugins. That pretty much answers my question. And thanks for helping out on other threads, the more the merrier 🙂

I knew you were replacing XXX with other text. What I was getting at relates to your other question about passing values. With filter hooks, you do not get to pick which parameters are passed, that is determined by the apply_filters() call. There is nothing in the ‘wp_login_errors’ hook that gives you any information about the user being registered, so it’s difficult to include any user specific information in this message (such as a phone number). You would be much better off if the message was more generic, like “Log in info sent to your phone via SMS”.

• This reply was modified 7 years, 1 month ago by bcworkz.

I like your plan! I agree that many plugins are just too feature laden. There’s always a need for super lightweight plugins that do one thing really well. I use Members intermittently on my test sites to help people with questions involving custom roles and capabilities. Much easier than writing the necessary code. Nice plugin. On client sites I write the code because it’s lighter weight 😉

I’m assuming you’ve managed altering the registration form so far by directly editing wp-login.php and you wish to identify the proper way to handle this.

In keeping with the lightweight concept, we shouldn’t modify the registration screen any more than necessary. I’ve covered the confirmation message. Other messages are likely managed in a similar manner, for example the password reset message is changed by adding the ‘newpass’ error message.

We can add additional registration fields through the “register_form” action. Simply echo out the all the field HTML from the callback. The added field data can be processed through the “register_new_user” action. The new user ID is passed to your callback. The field data should still be in the super-global $_POST array. The data should be validated and sanitized before adding it to the user’s meta data.

The sendtext() calls can be added to the various functions that compose and send the email messages. Since you are also sending email, you could just hook the “wp_mail” filter and sendtext() from there. The tricky part though would be determining which mail messages should be texted and which not. Hooking more specific functions may be a better choice. They typically have a usable action. If not they are possibly a pluggable function that a plugin can re-define.

There is invariably a hook to use for almost any situation. There is never any valid reason to alter core files. In some cases it may take some creativity to find a solution. I’m generally pretty good at that, so if you’re stuck, just ask!

You should have the clear impression by now that nearly everything in WP is managed through a filter or action hook of some sort. If you’re going to spend time learning something, getting a clear understanding of how filter and action hooks work and how to write callback functions would be a great place to start.