Do you have a WordPress site?
\nDo you run a business with hundreds or thousands of users?
\nThen, you might want your consumers to seamlessly move between your multiple sites without them having to re-enter their credentials, right?\nAsking them to re-authenticate is a cumbersome process. This is where SSO helps you!
\nBusinesses thrive by providing a seamless experience to their consumers. So, yes! Whether you are running an ecommerce business, travel, hospitality, or even blogging, you can only attract consumers to provide them with frictionless experiences.
\nSingle Sign-On (SSO) refers to the authentication process that allows your customers to access multiple applications with a single set of login credentials and an active login session.
\nHaving SSO for your WordPress sites will boost the experience of the consumer spending time on your site. It is relatively effortless nowadays to build a fancy-looking site that will attract consumers at first.\nBut, for a site to gain traction and make those consumers return to your site will be a challenge.\nFor example, by offering a frictionless experience and having no barriers like complicated registration forms, asking not to sign in repeatedly will make your site stand out over your competitors.\nSSO helps your consumers navigate across your multiple web properties. Once the user is logged in, they don't have repeated demands for sign-ins. The experience is frictionless.
\nAdding SSO to your existing web properties can be a challenge. LoginRadius WordPress Plugin is an out-of-box solution that replaces the WordPress default login form with the LoginRadius JS forms.
\nWith minimal time and effort, you can add SSO to your existing sites leveraging LoginRadius WordPress Plugin and gain access to login data via our dashboard. This will help you to boost conversion and also reduce the time to onboard consumers.
\nWe have detailed documentation.
\nLoginRadius aims to help developers, web development agencies, and businesses to add SSO in the simplest way possible.\nLoginRadius allows you to store your consumer profiles securely and add our customizable login interfaces into your applications in minutes. By enabling our SSO, you can create a frictionless user experience, thus boosting your conversion rate.
\nWe always want to hear from our customers. Like many others in the market, we want developers to install it and offer feedback. This feedback will help us enhance the plugin and make it more user-friendly. I often come across people and clients who would like to build their custom login, registration, and lost password form in WordPress instead of using the default wp-login.php page. It's probably because it's too wordpress-y. In this tutorial, I will demonstrate how to build a custom login form using the default functionality that wordpress gives us. This is what WordPress gives us out of the box. I am going to show you all of this tutorial using the page-theme method because it is probably the easiest to implement for beginners. This will also give you an intro into page themes, if your not familiar with it. To start our theme, you will need to do the following: To initialize this page template, make sure to activate the theme you've selected in \"Appearance/Themes\" in your admin dashboard and then navigate to a page or post. On the right hand side of your page/post editor you should now see a dropdown available for template under \"Page Attributes\". Change your template to \"Login\" or to the name that you specified in \"Template Name:\" and that will attach that page theme to this page/post. Now we're ready to start editing this page-login.php template file. So first open this file in your favorite editor and Let's get a login page started. To quickly show you how to get this login on the page Let's paste the following code between the div with id of content. Look at what that small piece of code do Now we need to set some arguments that we can provide to this form to customize it. Let's take a look at the documentation for wploginform() In that document, it explains all the uses and arguments of wploginform(). Let's use those arguments section and see what happens. Paste the $args section shown in the wordpress doc right above our login form. It will look the same as the one we did earlier but, by customizing the arguments above, you can customize elements of the login form. To handle the Login Form response we need to grab the $_POST parameters and login the user. You can create this as complex as you like, but I will demonstrate a simpler but effective method. For this action, we'll be using the aftersetuptheme and wp_authenticate. I have added the following two functions within the functions.php file. The first function optionalemailaddress_login searches for a users email address based on their username, with this functionality you can log in using your email address or the username. The second function, login_user, handles the actual functionality of the login by receiving the $POST parameters and passing them into the wpsignon method. In this example I have used the default WordPress login form that you could customize and style to your desire. In the next blog, I will be demonstrating how to build a login form that is fully customized. We won’t be using the provided wordpress functions! In this tutorial I want to explain the different methods to enqueue scripts and style sheets in WordPress. This can be a really confusing process for new WordPress developers. There are three different areas that a developer can enqueue scripts for; the first is the client side, the second is the admin side and the third is the login pages. Each of these areas uses a specific hook to enqueue scripts to use in that area. For example, if a script was enqueued using the login_enqueue_scripts hook that script would not be loaded in the admin area. This allows WordPress to load only the scripts needed for that specific section. Optimization! When you don’t enqueue scripts using these hooks and instead use the An example of the three enqueuing hooks are below: wp_enqueue_scripts hook – Front End admin_enqueue_scripts hook – Admin area login_enqueue_scripts hook – Login pages If you are calling the same script in many different areas you can register the script or stylesheet first and then use it when needed in your plugin. In the above examples you’ll notice the function being called is enqueuing a script or a style only and not registering a script or a style. When you register first it allows that script or style to be called in the area it was registered in when you enqueue it. Here’s an example of registering scripts first. In the example above you can see first I have registered the script then used wp_enqueue_script to enqueue it. You don’t need to enqueue the script directly after registering as a practice, however after registering the script you can enqueue it on pages you require it. If you have registered the script or style using wp_enqueue_scripts it will only be available on the front end of your site and not the admin pages or the login pages.\n
\nYour Take?
\nBuilding a WordPress Login Form (Out of the box)
\n\n
\n
\n<?php\n/*\nTemplate Name: Login\n*/\n \nget_header(); ?>\n \n<div id="primary" class="content-area">\n<div id="content" class="site-content" role="main">\n \n</div><!-- #content -->\n</div><!-- #primary -->\n \n<?php get_sidebar(); ?>\n<?php get_footer(); ?>
\n<div id="primary" class="content-area">\n<div id="content" class="site-content" role="main">\n<?php wp_login_form(); ?>\n</div><!-- #content -->\n</div><!-- #primary -->
\n<?php $args = array(\n'echo' => true,\n'redirect' => ( is_ssl() ? 'https://' : 'http://' ) . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'],\n'form_id' => 'loginform',\n'label_username' => __( 'Username' ),\n'label_password' => __( 'Password' ),\n'label_remember' => __( 'Remember Me' ),\n'label_log_in' => __( 'Log In' ),\n'id_username' => 'user_login',\n'id_password' => 'user_pass',\n'id_remember' => 'rememberme',\n'id_submit' => 'wp-submit',\n'remember' => true,\n'value_username' => '',\n'value_remember' => false\n); ?>\n<?php wp_login_form( $args ); ?>Handling the login form response (Custom)
\n
\n/**\n* optional_email_address_login allows the user\n* to log in with a email address as well as a username\n* @param string &amp;amp;$username username or email\n* @param string &amp;amp;$password password\n*/\nfunction optional_email_address_login( &amp;amp;$username, &amp;amp;$password ) {\n$user = get_user_by( 'email', $username );\nif ( ! empty( $user-&amp;amp;gt;user_login ) )\n{\n$username = $user-&amp;amp;gt;user_login;\n}\n}\n// Allows the use of email logins\nadd_action( 'wp_authenticate', 'optional_email_address_login', 1, 2 );\n \n/**\n* login_user handles the $_POST array and logs in users\n*/\nfunction login_user() {\nif ( ! is_user_logged_in() ) {\n$creds = array();\n$creds['user_login'] = isset( $_POST['log'] ) ? $_POST['log'] : '';\n$creds['user_password'] = isset( $_POST['pwd'] ) ? $_POST['pwd'] : '';\n$creds['remember'] = isset( $_POST['rememberme'] ) ? true : false;\n$user = wp_signon( $creds, false );\n \nif ( is_wp_error( $user ) ) {\nerror_log( $user-&amp;amp;gt;get_error_message() );\n}\n}\n}\n// Run login_user before headers and cookies are sent\nadd_action( 'after_setup_theme', 'login_user' );<script> tag, it can cause the script to be loaded every time you load the site, admin area or login page. This can cause conflicts with other scripts, plugins or themes. WordPress takes care of these problems when you use the hooks intended.
\nfunction themeslug_enqueue_style() {\n wp_enqueue_style( 'core', 'style.css', false );\n}\nfunction themeslug_enqueue_script() {\n wp_enqueue_script( 'my-js', 'filename.js', false );\n}\nadd_action( 'wp_enqueue_scripts', 'themeslug_enqueue_style' );\nadd_action( 'wp_enqueue_scripts', 'themeslug_enqueue_script' );
\nfunction load_custom_wp_admin_style() {\n wp_register_style( 'custom_wp_admin_css', get_template_directory_uri() . '/admin-style.css', false, '1.0.0' );\n wp_enqueue_style( 'custom_wp_admin_css' );\n}\nfunction my_enqueue($hook) {\n if ( 'edit.php' != $hook ) {\n return;\n }\n wp_enqueue_script( 'my_custom_script', plugin_dir_url( __FILE__ ) . 'myscript.js' );\n}\nadd_action( 'admin_enqueue_scripts', 'load_custom_wp_admin_style' );\nadd_action( 'admin_enqueue_scripts', 'my_enqueue' );
\nfunction themeslug_enqueue_style() {\n wp_enqueue_style( 'core', 'style.css', false );\n}\nfunction themeslug_enqueue_script() {\n wp_enqueue_script( 'my-js', 'filename.js', false );\n}\nadd_action( 'login_enqueue_scripts', 'themeslug_enqueue_style', 10 );\nadd_action( 'login_enqueue_scripts', 'themeslug_enqueue_script', 1 );
\nadd_action( 'admin_enqueue_scripts', 'my_plugin_admin_scripts' );\nfunction my_plugin_admin_scripts() {\n /* Register our script. */\n wp_register_script( 'my-plugin-script', plugins_url( '/script.js', __FILE__ ) );\n wp_enqueue_script( 'my-plugin-script');\n}