Yes, and no! The way users work in a multisite scenario is that there is a single pool of users, who are then associated with blogs. So, logged in status is common across all the blogs, but you can use is_blog_user($blog_id) to determine whether the current logged in user is a member of that blog. … Read more
The code he posted in that tutorial (very nice BTW) post’s the form to the build-in “reset password” module which redirects to the login.php on error, but you can change that and build your own based on the original and add it to the template page, change: <form method=”post” action=”<?php echo site_url(‘wp-login.php?action=lostpassword’, ‘login_post’) ?>” class=”wp-user-form”> … Read more
I found a solution. In wp-config.php add: define(‘FORCE_SSL_ADMIN’, false); In my situation, I migrated to https from http, and use plugin Rename wp-login.php My wp-config.php contained the lines: define(‘WP_SITEURL’,’https://example.com’); define(‘WP_HOME’,’https://example.com’); Without the line define(‘FORCE_SSL_ADMIN’, false);, a redirect loop occurs.
I’d recommend Auth0 plugin https://wordpress.org/plugins/auth0/ oAuth plugins should auto populate the data that your API call allows. And your users should be able to edit their profiles also. LinkedIn also has an AutoFill function here: https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/plugins/autofill-plugin
You just need to add your filter hook like this: function myplugin_cookie_expiration( $expiration, $user_id, $remember ) { return $remember ? $expiration : 600; } add_filter( ‘auth_cookie_expiration’, ‘myplugin_cookie_expiration’, 99, 3 ); You can add it to your theme’s functions.php file.
By default, WordPress makes your login session cookie expire in 48 hours (or on browser close), or 14 days if you check the “Remember Me” box. Maybe you have some plugins which force your login cookie to expire. You could manually add the code below on your functions.php to extend your cookie expiry to whatever … Read more
Basically to log a user in you can use: //Login the user $creds = array(); $creds[‘user_login’] = $login; $creds[‘user_password’] = $password; if ( !empty( $remember ) ){ $creds[‘remember’] = true; } $user = wp_signon( $creds, true ); but that is only when you have the password and login so you can create your own register … Read more
OK, the approach that’s working for me is as follows: Assume that the main site user database is authoritative. The main site login cookie contains an ID and a hash of the site password. Get the cookie from the main site and revalidate it against the main site’s authentication API If valid, use the email … Read more
Creating two separate registration for different roles is easy: //create a hidden field for role add_action(‘register_form’,’add_hidden_role_field’); function add_hidden_role_field(){ if (isset($_GET[‘role’])){ echo ‘<input id=”user_email” type=”hidden” tabindex=”20″ size=”25″ value=”‘.$_GET[‘role’].'” name=”role”/>’; } } add_action(‘user_register’, ‘update_role’); //save the the role function update_role($user_id, $password=””, $meta=array()) { if (isset($_POST[‘role’])){ $userdata = array(); $userdata[‘ID’] = $user_id; $userdata[‘role’] = $_POST[‘role’]; //only allow if … Read more
You can do that easily. You just need to specify a redirection parameter. If you are using a login link on the homepage to go to the login page, then @sisir’s solution is correct. <?php echo wp_login_url( $_SERVER[“HTTP_HOST”] . $_SERVER[“REQUEST_URI”] ); ?> If you are using a custom form on the frontpage, then inside the … Read more