TROUBLE SHOOTING GUIDE FOR LOGIN ONE! PLUG-IN
Login One! plug-in for Joomla! 1.6 / 1.7 / 2.5
This page is regularly reviewed. Based on customer queries that we have received, we may expand or alter it as needed.
The information presented here is to be considered a basic guideline and is provided 'as is', without any form of warranty or guarantee. We accept no liabilities for using the informations on this page.
This troubleshooting guide applies to all current Login One! editions and versions.
Authentication plug-ins are criticial pieces of software and your Joomla! installation and setup may be different from the basis for these instructions.
CHECK YOUR VERSION
Before anything else, make sure that you are using the latest version.
There is a 'version check' link in the plug-in management screen (back-end), under Description. Look for "Is this the latest version? Check it here".
MOST COMMON OMISSION / MISTAKE
The most commonly made omission / mistake is that the documentation which is included in the downloaded package is not read. At least half of the requests for help that we receive could be simply answered by the famous initialism RTFM.
Some of the obvious solutions, even if already mentioned in the plug-in documentation, are included in the guidelines below.
When the install package size exceeds the maximum allowed upload size set by PHP, Joomla! will throw an error and the plug-in package will not be installed.
- The install file size exceeds the configured maximum of the PHP upload size of your website or ISP.
- If you have access to the PHP configuration, increase the settings of upload_max_filesize and post_max_size in the file php.ini, OR contact your ISP to do this for you.
This is the recommended solution, because the install package size is not really that big, so you will likely experience this problem with other extensions as well, sooner or later.
- Workaround if the above solution fails: remove the documentation (PDF) files from the installation (ZIP) file and retry. Make sure to keep a copy of the original installation file!
Though this is not directly related to errors and trouble, we'd thought it would be wise to mention it anyway.
After having installed and enabled the plug-in (see documentation), you should check - BEFORE you log out from the back-end - whether you will not be locking yourself out from the front- and back-end:
- While leaving the back-end open, open the website's home page (front-end) in a separate tab or window, for example by clicking the Preview or View Site link at the top of the back-end page.
- Log into the home page (front-end), not necessarily as an administrator, and log out again.
- If you see no errors upon logging in or out, you are OK. You may log out from the back-end.
- If you see errors upon logging in or out, disable both the Login One! authentication and user plug-ins and enable the standard Joomla! authentication and user plug-ins instead. The Login One! plug-in is not functioning correctly.
You can't get access and you are seeing a notice telling you that your username/password are wrong or that you do not have an account.
- You have most likely not carried out the installation check mentioned under 1.
- If you see an error saying "Could not load authentication libraries", you have probably disabled the standard Joomla! authentication plug-in while not having enabled the Login One! plug-in.
- You are not using the latest version of the plug-in.
- If you are still logged into the back-end, it's your lucky day. Check the version of the plug-in and update both the athentication and the user plug-in if necessary. Then make sure that both the Login One! authentication and user plug-ins are enabled.
- If you have logged out from the back-end and can't get back into the back-end, there is no other way than to regain access by directly editing the MySQL database of the website, see Regaining back-end access after lock-out. After this, you can enable the Login One! authentication and user plug-ins through the back-end.
Even after waiting ages for the other session to expire, you can't get access to your website and the Login One! plug-in continues to notify you that multiple log-ins are not allowed.
- Another session using the same user credentials is still open and the other session is either still active or the website has been configured with a very long session life time.
- The website does not have the overrides installed and the standard Joomla! install keeps the other session alive even if it's not active any longer (see here for more info about this behaviour).
- You are not using the latest version of the plug-in.
- Reduce the session life time in the website global configuration.
- Check the version of the plug-in and update both the athentication and the user plug-in if necessary.
- Install the overrides (Premium and Business Editions only). The Login One! freeware editions do not have the override option.
The following applies to the Business Edition only.
Despite that you have configured the 'maximum allowed sessions' to a value of 2 or greater, the plug-in is blocking all multiple log-in attempts.
- You have not configured any allowed user groups, meaning that no user groups and therefore no users are allowed to have multiple log-ins. This is the default behaviour of the plug-in.
- Configure the option named 'Allowed user groups' (near the top) and select there which user groups will be allowed multiple log-ins according to the set 'maximum allowed sessions'.
NOTE: Including the user group 'Public' in the selection will disable the option.
The plug-in is rightfully denying access to multiple log-in attempts, but the notification that multiple log-ins are not allowed is not displayed at the front-end.
- Your website is using a template that does not have the system messages included correctly.
If the website is using the standard Joomla! login module, you can check this by logging in while using 'gibberish' credentials, e.g. username xxx and password xxx. You should see a message saying that your credentials are wrong. If not, the front-end template is likely the problem.
- It is not the Login One! plug-in but some other extension that is denying access.
- Modify the template to properly include system messages.
The body should include the code <jdoc:include type="message" />
- Enable the standard Joomla! authentication and user plug-ins. Then disable the Login One! plug-ins (both authentication and user) and check again.
- The user being blocked has been assigned to two or more User Groups and the option User Group Priority is set to 'most restrictive'.
- Allow multiple log-ins to the other User Group(s) as well, OR set the related User Group Priority to 'least restrictive'.
- The authentication plug-in has not been enabled/published.
- You have not disabled the standard Joomla! authentication plug-in.
- You are using a Super User account. Super Users are never blocked.
- You are not using the latest version of the plug-in. Check the version of the plug-in and update both the athentication and the user plug-in if necessary.
- The plug-in scope has been set incorrectly, for example to 'back-end only'.
- Your account has been allowed multiple log-ins, see plug-in configuration.
- You are logging in from the same workstation while the plug-in Strict Mode has been set to NO.
- The authentication plug-in is not fired first; put it at the top of the plug-in list.
- Something went wrong during plug-in download and/or installation: download and/or install both plug-ins (authentication and user) again.
- The Joomla! Session Handler configuration has been set to "PHP" or "None".
- Set the Joomla! Session Handler to "database" (Back-end admin / Global config / System).
- The installed Joomla! update has probably changed the user log-in/log-out process in a way that is not compatible with the Login One! plug-in. For this reason, we recommend to always check and update the plug-in BEFORE updating the Joomla! core.
- If the plug-in is now locking you out from the back-end (you see an error or the notice that your credentials are wrong), try to get access to the back-end through a Super User account. If this does not help, then see under Regaining back-end access after lock-out.
- If the plug-in is not locking you out from the back-end, but is merely performing incorrectly, then check for plug-in updates and install the latest updates if available. If things are still not OK, you may check the other cases in this guide, or have a look at the plug-in documentation, or have a look at the forum, or contact us for support (Premium and Business Editions).
Possible causes and solutions:
- This is the correct behaviour of the Standard (freeware) Edition
The following is for the Premium and Business Edition only:
- You have not installed the so-called override or the current override has become inactive because you have updated the Joomla! core software. Log into the front-end with Super User credentials, then log out and try again with the other account. If this doesn't work, uninstall and re-install the Login One! override, see documentation.
- The current override may have become inactive because you have installed/updated a 3rd party login extension. Uninstall and re-install the Login One! override, see documentation.
The following applies to the Business Edition only.
You have configured the plug-in notification to NOT show the notification part 2 that specifies the remaining waiting time; despite this, the message is still being shown.
Possible cause and solution:
- This option has been introduced with Joomla! 2.5.28 and was bugfixed in plug-in version 2.5.1. Solution: Update your Joomla! to v2.5.28 and the plug-in to version 2.5.1 or later.
If all the above does not apply or has not solved the problem, then you may want to try this.
- Your Joomla! install may be using the PHP Session Handler.
- Your PHP version is outdated.
- There is a bug in the extension.
- Check how the Joomla! Session Handler has been configured. The setting can be found (and changed) at the back-end under Global Configuration / tab System / Session Settings.
If you set the Session Handler to 'Database', the problem may be gone. If the Session Handler has already been set to 'Database', then do NOT change it.
- Use a newer PHP version. Many ISPs provide an option in their admin panel to select the PHP version.
- Please contact us and tell us what you have observed. Do not forget to include your Joomla!, PHP and extension edition and version.
If you are using the Standard (freeware) Edition, you can skip this, because the freeware edition does not have the Login One! override.
- Log into the front-end with user credentials that are not allowed simultaneous sessions.
- Log into the front-end website with the same user credentials but using a different browser.
- You should see a notification saying that the second log-in has been denied.
- If the last sentence of this notification specifies a waiting time (in minutes), then the Login One! override is active.
Note: The plug-in scope configuration must include the ‘front-end’.
This is a last-resort option, if anything else has failed.
You will need MySQL access to the database of the involved Joomla! website.
- Use MySQL Admin, phpMyAdmin or another MySQL program to connect to the website database.
- Open the table named prefix_extensions. The word prefix will have been replaced by some code.
- Look for the extension named plg_authentication_joomla , get into the edit screen for this record and set the enabled field to 1. Save the record.
- Next, look for the extension named plg_user_joomla , get into the edit screen for this record and set the enabled field to 1. Save the record.
You have now re-enabled the standard Joomla! access plug-ins. Try if you can get access to your website.
If you still can't get access, then you must additionally disable the Login One! plug-ins in a similar procedure:
- Connect to the Joomla! database and open the table named prefix_extensions.
- Look for the extension named Authentication - Login One! (or similar), get into the edit screen for this record and set the enabled field to 0 (zero). Save the record.
- Look for the extension named User - Login One! (or similar), get into the edit screen for this record and set the enabled field to 0 (zero). Save the record.
Your website has now been configured as if the Login One! plug-ins have not been installed.
If you still have no access, front- or back-end, the problem lies somewhere else, i.e. not with the Login One! plug-ins.
16 Nov 2018