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 ); wp_set_auth_cookie( $user_id ); wp_redirect( home_url( ‘/some-ending-page/’ ) ); exit(); } add_action( ‘user_register’, ‘automatically_log_me_in’ ); Long answer – here is an explanation of why this is the answer. … Read more
wp_users is the primary table, with a fixed list of columns. wp_usermeta is an additional table for storing arbitrary information (custom fields). The wp_users table already has a user_email column, so I don’t know why the plugin uses wp_usermeta. The best person to ask would be the plugin author himself.
ReAuth=1 is required when your login Cookies are no longer valid, WordPress will force validation for your browser. if ( $force_reauth ) $login_url = add_query_arg(‘reauth’, ‘1’, $login_url); Add reauth=1 flag to login url when auth_redirect() redirects to wp-login.php after the auth cookie fails validation wp-login.php clears cookies and forces log in if reauth=1. If reauth=1 … Read more
finally this is working for me on my local WP installation after replacing – with _ from input attribute name and using full php start tags <?php instead of <? the final code is here copy and paste into your template. <?php if ( isset($_POST[“user_email”]) && isset($_POST[“user_password”]) ) { $user_login = esc_attr($_POST[“user_email”]); $user_password = esc_attr($_POST[“user_password”]); … Read more
WordPress handles login failed in two ways: If it is a bad credential, and both username and password have a value, then this action can be captured by wp_login_failed If both, or one, of the options are empty, then WordPress generates the error object as the first parameter in the authenticate filter; it does not … Read more
For me, the solution to this WordPress Login loop problem was in the database.So step one is to login to the database. I just used PhpMyAdmin for this.Once logged, find your WordPress table, and navigate to the wp_options table. There are two fields in this table that could be the culprit to your WordPress Login … Read more
If you look at the code for wp-login.php both the login case and the default case run wp_signon(). The reason, so it seems to me, is to manage cases where a user already has a valid cookie for the site. So I don’t think there is a hook that fires only upon login, but it … Read more
just add the following code to your function.php. it will redirect back user from where the login form is submitted. add_action( ‘wp_login_failed’, ‘my_front_end_login_fail’ ); // hook failed login function my_front_end_login_fail( $username ) { $referrer = $_SERVER[‘HTTP_REFERER’]; // where did the post submission come from? // if there’s a valid referrer, and it’s not the default … Read more
Investigating the filter authenticate, we can find that it is called inside the function wp_authenticate, which is a pluggable function. That means that it can be replaced by one of our own making. This is the original function, plus a marked entry point: function wp_authenticate($username, $password) { $username = sanitize_user($username); $password = trim($password); $user = … Read more
I’m not sure I understand your setup, but here are few ideas: A) Display a login link with the redirect_to parameter set: You could add the following to your custom template pages: if( ! is_user_logged_in() ) { printf( ‘<a href=”https://wordpress.stackexchange.com/questions/169704/%s”>%s</a>’, wp_login_url( get_permalink() ), __( ‘You need to login to view this page!’ ) ); } … Read more