Search Results

Depending on the flexibility of your plugin, you could add a CAPTCHA to the registration, and/or you could add a "honey pot." In terms of blocking registration spam, a honey pot is essentially a regul …

As one other answer noted, you can alter the wp_new_user_notification() function since it is pluggable. But it also has a filter hook wp_send_new_user_notification_to_user in it to stop the notificat …

Here's a basic approach. First, you would need to pass something in the link to give some user info you can use to log the user in. To do this, you need to filter the email that goes to the user. (I …

Actually, the arguments you are passing for the wp_new_user_notification() function are incorrect - it requires the user ID, not the username. Also, that may not be what you want to use in this case s …

If this is being run when you register a user, then you could just grab the email used in creating the user as it is contained in the second argument that is passed to user_register which is $userdata …

I was led to this post while doing a Google search for a particular email question. Funny thing was that the posted answer references one of my blog posts and my plugin. That's kind of awesome - exc …

@Brady's answer is correct because WP-Members does use WP's function for inserting a new user, so that action does get called. And if you want flexibility and you are only using the new user's ID for …

There is actually nothing wrong with the code that you have (I tested it as you have it above and it works fine). But you have to account for some additional possibilities: The wp_new_user_notifica …

The function that generates the new user notification is wp_new_user_notification(). It is called by another (similarly named) function wp_new_user_notifications() which is triggered by the action ho …

I'm not entirely clear on what you're trying to do, but it seems you want to pass the user's email address via a query string and determine the user by that. You can get the user's ID for writing use …

There is nothing in plain vanilla WordPress that would result in what you described. It would seem that your problem stems from customizing your process (either by plugin or by your own customization) …

There are a number of issues with the user of update_user_meta() in your function. First, you should never write the value directly from $_POST without sanitizing it first. That's a good way to open …

Sometimes you have to look at the name of the input you're trying to pick up via $_POST. It's not always consistent across forms. In the case of the WooCommerce password change form, the input name …

Short answer - Your original function (mostly) works. This is your function edited to do what it needs to do: function automatically_log_me_in( $user_id ) { wp_set_current_user( $user_id ); …