Shop is closed.
Due to health issues support is very limited
FAQ's
Installation / update
What are the system requirements?
- Joomla 1.5 or 2.5 or 3 fully and correct installed
- PHP 5 or later
Error: 'Could not create directory, Warning! Failed to move file'
Check your directory premissions:
'help' > 'System info' > 'Directory Permissions'
All least these folders should be writeable:
- administrator/components/
- administrator/language/en-GB/
- components/
- plugins/
- plugins/system/
- plugins/user/
- tmp/
You can also enable the FTP layer and try to install again.
Error: 'Path does not point to a valid folder' 'Could not find a Joomla! XML setup file' 'File...does not exist'
You are probably dealing with a corrupt download. Both Symantec and McAfee are known to corrupt downloads with certain settings. They can also corrupt the extensions send and received by email. So try this: go to the download area, disable the firewall/virusscanner, download the file, enable the firewall/virusscanner. If you are on a network when you can not disable the fireall/virusscanner, there is no orther option but to download the extension using another computer.
How to update?
- Download the component.
free- and trial-version
pro-version - Install the component over the old component (no need to uninstall first).
This will also install the 2 Redirect-on-Login plugins (system and user)
If you get an install error, there is probably a right issue with the files and folders. In that case, try installing with the FTP-layer enabled.
If the component installs well, but not the 2 plugins, you can install those seperately.
If you are updating from free- to trial-version, or trial- to pro-version, just install the new version over the old version.
All configuration and settings will remain in the database.
Do I lose my settings and configuration when updating or upgrading?
No. All configuration and settings will remain in the database.
If you are updating from free- to trial-version, or trial- to pro-version, just install the new version over the old version.
End faq
Configuration
Login after no-access does not go to previous page
A not logged in user tries to go to a restricted page, then logs in but does not get redirected to the page the user was trying to get to. If you want the user to go back to the previous page, configure this in the Redirect-on-Login configuration at 'Login after no access to page' select 'to the page'.
If that does not work, check if your template shows a message when trying to go to the restricted content. It should say something like 'Please login first'. Redirect-on-Login needs this message on the page to know there was a no-access-event. If you are not sure, try to login at the frontend with a wrong login. You should see a message 'Username and password do not match or you do not have an account yet.' If you do not see such a message, your template needs to be fixed. This happens a lot in old templates which have been updated to joomla 3. How to fix your template messages.
If the message is there but it does not redirect to the previously restricted page, please check if any redirect is set via any other extension. If so, disable those extensions. Check the login-menu-item redirect settings is empty, and the login module redirect settings are empty. Please note module bt_login of Bowthemes is incompatible.
If the user still does not gets redirected to the previously restricted page. Please test with the default Joomla template 'protostar', just to make sure it is not a template or template related login module or plugin which is causing this.
If you are redirecting to a Edocman download, please consider that Edocman redirects to a relative file in the document download view. If you would decode the base 64 encoded url, it seems to be missing the whole http:// part of the url. Here is how.
If that does not work AND you got Community Builder installed, you need to edit the CB settings.
Community Builder has a plugin which actually destroys the return url. To stop community builder from doing that:
- go to the plugin manager
- open the plugin 'Community Builder System plugin'
- go to tab 'Parse URLs'
- at 'Pass Return URLs' select 'disabled'
- click 'save and close'
I have blocked all backend access, now I can not login anymore. How to fix this?
- Use FTP and rename this file:
administrator/components/com_redirectonlogin/plugin_user/plugin_user.php
This will disable all redirections and also the blocking of the access to /administrator. - Then login and change your settings. Make sure at least one super-administrator is not blocked.
- Rename the file back to plugin_user.php
The redirect from another extension is used, not the redirect as set in Redirect-on-Login.
There are 2 things you can do:
- Disable the redirection from the other extension, or disable that extension.
Then only the redirects as set in Redirect-on-Login will be used. - Make sure in the login-module and the login-page menu-item have no redirect set for when logging in.
- In the plugin-manager, filter on 'user'-plugins and make sure the Joomla!-plugin is first in order and the Redirect-on-Login user-plugin is second in order.
Then the redirect as set in Redirect-on-Login will override the other extensions redirect. When redirect is set to 'normal' (in 'configuration' AND 'usergroup' or 'accesslevel' AND 'user') then the redirect as set in the other extension will be used.
The redirect goes to the profile page instead of the configured redirect.
You probably are redirecting to a (SEF) url which does not exist in Joomla. ROL redirects to the correct url (see in the adress-bar of your browser), but Joomla does not recognize the (SEF) url, and displays the default, which is the users profile page.
To solve this:
- Create a menu-item or url to which you want to redirect
- Go to the menu-item/url in your browser
- Copy the url and paste as the url to redirect to in ROL
Error when using a dynamic redirect
- Please double check that in the dynamic redirect the $redirect_url is NOT a SEF url. The redirect_url should be a non-sef url. Example: 'index.php?option=com_something&view=something&Itemid=23'
- Make sure the user has access to the page you are redirecting to, else you get a 403-error.
- When creating a link from content to a dynamic redirect make sure you are using the right url to the dynamic redirect.
Example: 'index.php?option=com_redirectonlogin&view=dynamicredirect&id=12' (where 12 is the id of the redirect).
Site is offline, redirect does not work
To test this, you can temporarily assign a test-user also to group 'administrator' so the user will be allowed to log into the disabled site.Please note that a user can be assigned to more then one group, in that case the redirect of the group highest in order on the ROL > 'usergroups' page is used. So to get a test going, set the order of 'administrator' to 200, so the redirect for the (frontend) group is used instead of the redirect for 'administrator'.
Create a link which does not redirect (for links from newsletters etc.)
index.php?option=com_content&rol=no
This can be used for links from newsletters etc. to not redirect when opening the site/logging in/logging out.
example code:
$redirectUrl = 'index.php?option=com_content&view=article&id=1&Itemid=108&rol=no'; $redirectUrl = urlencode(base64_encode($redirectUrl)); $redirectUrl = '&return='.$redirectUrl; $joomlaLoginUrl = 'index.php?option=com_users&view=login'; $finalUrl = $joomlaLoginUrl . $redirectUrl; echo 'http://domain.com/'.$finalUrl;
Stay on current page when using login module, go to previous page when coming from the login-page?
If you want the user to stay on the same page during login, except for on the login-page, where you want the user to return to the previous page.
Create a dynamic redirect named 'set previous page' which contains this code:
$app = JFactory::getApplication(); $app->setUserState( "com_redirectonlogin.previouspage", $current_url);
Configure the above script to run on each pageload.
Go to 'Redirect on Login' > 'all users' > 'frontend' at 'run script' and select the above script.
Create another dynamic redirect named 'go to previous page' which contains this code:
/*only set redirect when coming from login page*/ if(JRequest::getVar('Itemid', '')=='233'){ $app = JFactory::getApplication(); $redirect_url = $app->getUserState( "com_redirectonlogin.previouspage", ''); }else{ $redirect_url = $current_url; }
Change 233 to the menu-item id of your login page.
Select the above dynamic redirect script for 'all users' > 'frontend' at 'Default redirect type on login'.
Or select this redirect per usergroup/accesslevel or user.
Override blocked login message in the language manager
- go to 'extensions' > 'Language Manager' > 'Overrides'
- select the language you want to set the override for (site)
- click 'new'
- enter the 'language constant'
when blocking login at the frontend that is COM_REDIRECTONLOGIN_YOU_CANT_LOGIN_FRONTEND
when blocking login at the backend that is COM_REDIRECTONLOGIN_YOU_CANT_LOGIN_BACKEND - enter the text to override
- click 'save & close'
Redirect 'when opening site' does not seem to work
The redirect when opening the site is triggered when the site is opened in a new browser session. So if you already had the site open in your browser-window, close the window and any other window of the same browser (or else the session is still there). Then open the browser again and go to your site. The 'redirect on opening the site' is then triggered.
If you find it is still not working, the Joomla cache might be interfering. In Joomla 'global configuration' > 'system' set 'System Cache' to 'Off - Caching Disabled'.
Language changes when user is logging in
In the Joomla plugin manager > plugin 'Syetem - Language Filter' in the configuration at 'Automatic Language Change' might be set to 'yes'. So when the user is logging in, the selected language is changed to the language as set in the user-manager for that user. If no language is set there, the sites default language will be used.
If you don't want the users selected language to change when they login, make sure 'Automatic Language Change' is set to 'no'.
More elaborate messages when login is blocked
You can configure more elaborate messages when a user is blocked by creating a dynamic redirect.
See 'dynamic redirects' > 'new' example 11 and 14.
$message = 'Hello '.$user_name.' you can't login here.'; $logout = 1; $redirect_url = $current_url;
Run script on each page load
On adminpage 'Redirect-on-Login' > 'all users' > 'frontend' you can select a script to be run on each page load. This can be used for redirecting a user to a country-specific subdomain.
if($country_code=='FR' && $_SERVER['SERVER_NAME']!='http://fr.domain.com'){ $redirect_url = 'http://fr.domain.com'; } if($country_code=='NL' && $_SERVER['SERVER_NAME']!='http://nl.domain.com'){ $redirect_url = 'http://nl.domain.com'; }
Or use this for any other process.
After wrong password, wrong redirect or error 404
The redirect url probably contains a slash (index.php/info) and/or is a SEF-url (search engine friendly). Please find the menu-item in the menu-manager and copy-paste the non-sef url from the 'Link'-field (triple-click to select)
Jomsocial Facebook connect
problem: error message when login first time with jomsocial facebook connect when trying to import avatar or status
After login the plugin is trying to reload the page to upload/import the avatar or status data (wrong!). Obviously Redirect-on-Login is on the case and starts redirecting. Thus the import fails.
solution: make the redirect a dynamic redirect script in ROL. So you can point to the redirect via an url. Then configure plugin 'System - Jomsocial Redirect' to redirect to that url after login. You can't enter an url in the plugins' configuration, only menu-items. Fortunately, you can make a menu-item to the Redirect-on-Login > dynamic redirect. To hide that menu-item from any menu, you can create a new menu called 'hidden' and add the menu-item. Don't forget to set the original redirect in ROL to 'normal', so jomsocial/facebook plugin can do its reloading outside the Joomla system and afterwards point to the script which seems to do the redirect just fine.
"Error: You are not authorised to view this resource"-message on login with correct redirect
There is probably another redirect set, outside Redirect-on-Login, to a page for which the user has no access. Make sure the login-page-menu-item has no redirect set. Also check login module.
Another issue could be if the login menu-item is not set to 'public'. if that is the case read this FAQ.
User is assigned to multiple groups/levels. How to get it to redirect using the correct group/level-redirect?
If a user is assigned to multiple groups, the redirect is used from the group first in order on the usergroup page. See your-domain/administrator/index.php?option=com_redirectonlogin&view=usergroups read the text under 'ordering frontend'. Edit the number of the ordering and to save the ordering, click on the small save-icon next to 'ordering frontend'.
Same for levels.
End faq
Pre/post sale
On how many website can I use the pro-version?
There is no limit. Use it on as many sites as you like.
Is the pro-version encrypted?
no.
Does the pro-version need Ioncube?
No.
free-version pro-version, what is the difference?
With Redirect-on-Login you can set redirects for:
free | pro | |
---|---|---|
Frontend redirect on login | ||
for all users | x | x |
per usergroup (if user is assigned to 1 usergroup) | x | x |
per usergroup (if user is assigned to more then 1 usergroup) | x | |
per accesslevel (if user is assigned to 1 accesslevel) | x | x |
per accesslevel(if user is assigned to more then 1 accesslevel) | x | |
per user | x | |
Backend redirect on login | ||
for all users | x | |
per usergroup (any number) | x | |
per user | x | |
Redirects on logout | x |
free | pro | |
---|---|---|
Frontend redirect on login | ||
for all users | x | x |
per usergroup | x | x |
per user | x | |
Backend redirect on login | ||
for all users | x | |
per usergroup | x | |
per user | x | |
Redirects on logout | x |
I purchased this extension, how to download?
After payment is confirmed you login and click in the right column on 'my extensions'. Then click on your purchase and download the files.
End faq
Known issues
Template does not display messages
Try to login at the frontend with a wrong login. You should see a message 'Username and password do not match or you do not have an account yet.' If you do not see such a message, your template needs to be fixed. This happens a lot in old templates which have been updated to joomla 3.
- Open templates/templatename/index.php
- find this code
<jdoc:include type="component" />
- replace with this code
<jdoc:include type="message" /> <jdoc:include type="component" />
Conflict with Google analytics when redirect when opening site
There seems to be a conflict when a redirect is set for when opening the website with some plugins for Google analytics asynchronous services.
"Error: You are not authorised to view this resource"-message when login page is not set to 'public'
I have yet to reproduce this, but on a website this message appears after succesfull login. The login page was set to 'guest' so the login menu-item would not display after the user was logged in. Somehow during the login process, the login-page was loaded, for which the user had no access and thus this message was displayed, even after the user was redirected to the correct page.
workaround:
You can set the login-page to 'public' and move the menu-item to a hidden menu (create new menu, call it 'hidden' and just don't display it via a module). So it is not displayed to anyone. Then create an menu-item alias (menu-type: system > alias) and set that to 'guest' in the visible menu. Errors gone.
Conflict with plugin 'User Hooks'
There seems to be a conflict with a user plugin named 'User Hooks'. I can't find it in the Joomla extension directory or in Google. Solution is to disable that plugin.
Conflict with module 'bt_login' from Bowthemes
There seems to be a problem with module bt_login. When a user tries to view a registered page without being logged in, then on the login page the return-url is encoded in a format which makes it not compatible with other Joomla extensions. The encoding should be in base64. Solution is to disable that module. Or use another template.