The Front End Login module lets you put login forms anywhere on your WordPress site; it also allows you to restrict access to verified users. Once enabled, several features become available: a [uo_login] shortcode for login from any page; a [uo_login_ui] for the default login page (which replaces wp-login.php and must be defined in the feature settings) and user verification.
Let’s start with verification. If enabled in the Settings (click the Gear icon to turn this on), users that register from the front end MUST be manually approved by an administrator before they can sign in. This field must be checked for it to work. Once set and saved, a “Verified” column will be added to the list of users in WordPress. Any users listed as “Not Verified” cannot sign into WordPress. To verify a user, navigate to the user’s profile and look for the “Verify User” label. By selecting this field and saving the page, the users will be able to sign in. On verification, users will also be notified by email that the account has been verified and access has been granted. If you turn this feature on, make sure you verify all existing users, including administrators!
The [uo_login_ui] shortcode allows you to replace the default wp-login.php page with your own branded page. To set this up properly, we recommend creating a page first and adding the [uo_login_ui] shortcode to a page. Once that’s done, return to the Uncanny Toolkit Settings page and open the settings for Front End Login. Choose the page you added and save the settings. Once this is set up, users will be directed to the new branded login page instead of wp-login.php. Both the [uo_login_ui] shortcode and the page must be set up for this to work properly. The login page must also be set up for the user verification to work.
Important: If you define a Login page in the Toolkit settings and don’t include a login form on that page, you can lock yourself and other users out of the site. Make sure the login form is on the page and working before you choose a Login page! We recommend testing in an incognito window if there are problems so that you’re still signed in as an administrator if you need to make changes. (If you do accidentally lock yourself out, delete or rename the Toolkit folder via FTP, sign in, re-enable the Toolkit and then add the login form properly.)
Also make sure that your login page is not cached. If you see redirect errors or users can’t sign in properly, check this first. Your host may also have server-side caching enabled for your login page (WP Engine and Siteground are known to do this, as are many others), so check with them if you’re not sure.
To add a simple login form to any page, use this shortcode example: [uo_login]content if logged in [/uo_login]. That allows you to add the form and include a special message to users seeing the form area that have already signed in (which replaces the “content if logged in” text”).
[uo_login]content if logged in [/uo_login]
Overriding the login template
For advanced developers, there’s a filter available to override the login template file with a file of your own. Here’s how you could replace the default template file with one in your child theme folder:
add_filter( 'uo_login_ui_template', get_template_directory() . '/my_template_file.php' )