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
Absolutely YES, you can achieve this. Rule 1: WordPress requires a username. We must provide a username. Rule 2: Don’t edit WordPress core code. We can achieve this by hiding username field, get email and store it as username. Step-1: Remove Username textfield add_action(‘login_head’, function(){ ?> <style> #registerform > p:first-child{ display:none; } </style> <script type=”text/javascript” … Read more
Firstly, you need to add the following capabilities to the Doctor and Receptionist role: list_users edit_users create_users delete_users Now we can get to work with controlling which users they can create/edite/delete. Let’s start with a “helper” function that will return which roles a user is allowed to edit: /** * Helper function get getting roles … Read more
Well the second bit of code is technically the correct way to do it. However, at the end of the add_settings_field() you can pass arguments. Please view the WordPress Add_Settings_Field function reference. This will help you in getting the best understanding of how the add_settings_field() function really works. Now, with that said, you could use … Read more
The process involves 2 steps: show the frontend form save the data on submission There are 3 different approach that comes to my mind to show the frontend: use the built-in registration form, editing styles, etc to make it more “frontend like” use a WordPress page/post, and display form using a shortcode use a dedicate … Read more
Use the global $pagenow, which is a common global set by WordPress at runtime: if ( $GLOBALS[‘pagenow’] === ‘wp-login.php’ ) { // We’re on the login page! } You can also check the type of login page, for example registration: if ( $GLOBALS[‘pagenow’] === ‘wp-login.php’ && ! empty( $_REQUEST[‘action’] ) && $_REQUEST[‘action’] === ‘register’ ) … Read more
The new user email is sent using the wp_new_user_notification() function. This function is pluggable, which means that you can overwrite it: // Redefine user notification function if ( !function_exists(‘wp_new_user_notification’) ) { function wp_new_user_notification( $user_id, $plaintext_pass=”” ) { $user = new WP_User($user_id); $user_login = stripslashes($user->user_login); $user_email = stripslashes($user->user_email); $message = sprintf(__(‘New user registration on your blog … Read more
Basically, this is a programming pattern for namespacing code within a WordPress plugin. Typically, you can only have one function called init() in a program, but more than one author will try to use that name. Placing function names in a class is a way around this limitation. For example: class Towfiq_Person { static function … Read more