You can use the wp_loaded hook to push all non-logged-in traffic to the login screen. Note how I’ve passed $_SERVER[‘REQUEST_URI’] to wp_login_url() – this is passed as a URL parameter to the login page, and once a user successfully signs in, they’ll be redirected back to the URL they were originally trying to visit. function … Read more
You also need to define a matching COOKIEHASH for both sites – a random 32 bit string will do. By default, COOKIEHASH is an MD5 hash of the site URL, and is used to generate the default names for all authentication-related cookies. Hence why, at the moment, your cross-domain login isn’t working (the names of … Read more
Yeeey, I figured it out! Actually my theme had a redirect like this one in functions.php: // Block Access to /wp-admin for non admins. function custom_blockusers_init() { if ( is_user_logged_in() && is_admin() && !current_user_can( ‘administrator’ ) ) { wp_redirect( home_url() ); exit; } } add_action( ‘init’, ‘custom_blockusers_init’ ); // Hook into ‘init’ All you have … Read more
You can use add_query_arg() to add any query parameters you want to a URI, e.g., $redirect_uri = add_query_arg (‘page’, ‘4’, get_permalink ()) ; $login_uri = wp_login_url ($redirect_uri) ; Or, you could simply use $_SERVER[‘REQUEST_URI’], which will already contain any query string present in the current page’s URI, e.g., $login_uri = wp_login_url ($_SERVER[‘REQUEST_URI’]) ;
Yes it’s also possible for the password, by running a filter on lostpassword_url, which is basically the password equivalent of the login url.. Example Basically the same as before, just changed the function and hook names. add_filter( ‘lostpassword_url’, ‘custom_lostpass_url’ ); function custom_lostpass_url( $lostpassword_url ) { return get_option(‘siteurl’). ‘/lostpass’; }
your code is correct, however, that filter only applies to the wp_login_form() function, which is not what wp-login.php uses, so you won’t be seeing your text there if that’s what you’re expecting! try adding a call to wp_login_form() in a template to see what the filter does.
If you read the documentation on wp_login_url, you can specify a redirect URL without having to use that hidden input field. Alternatively, you could just use the wp_login_form function to do exactly what you want: <?php wp_login_form(); ?> Just toss that in there in place of your form, and read the documentation on that function … Read more
Since version 3.4 (or earlier?) WordPress sends a special HTTP header (not in HTML) on login and admin pages: X-Frame-Options: SAMEORIGIN So your browser will show you some text built into the browser, not sent from WordPress. From wp-includes/default-filters.php: add_action( ‘login_init’, ‘send_frame_options_header’, 10, 0 ); add_action( ‘admin_init’, ‘send_frame_options_header’, 10, 0 ); You could create a … Read more
If I were you, I would use the wp_login_form function to create your form, but it looks like you got everything right, and maybe you have a good reason to use a manual form. <?php wp_login_form(); ?> Either way, you can use this action to update the login redirect, add it to functions.php: add_action( ‘login_redirect’, … Read more
The resolution is pretty simply. Those functions require the passwords to be properly escaped. So Instead of this: wp_set_password(‘Test”123’, $userId); You have to do this: wp_set_password(wp_slash(‘Test”123’), $userId); The same goes for wp_update_user() and wp_signon(). Further information and updates on the docs may be visible from this bug report: https://core.trac.wordpress.org/ticket/34297#ticket