Configuration
Backend module does not show in module-manager
The module is a backend-module, so go to the module-manager, and click on tab 'administrator'.
AUA does not work with my template
The AUA backend module needs to be published to the same position as the Joomla menu. In the default Joomla installation that is 'menu'. Some template makers use different module-position names. So in the module-manager, click on 'administartor' to see the backend modules. Find the Joomla menu-module (disable/enable it so see if you got the right one) and check the position it has. Then assign the AUA module to that same position.
Will users not connected to a usergroup have access?
No, except for super-administrators.
If the restriction-type (page access, itemtype access, component access etc.) are activated in the Admin-User-Access configuration, any user connected to a group with no access or not connected to a group at all will not have access.
I gave a group access to a page but they can't access it.
You might also have workflow settings active which prevent access to pages. Check workflow-settings 'edit-content-page' and 'edit-link-page' for that group.How do I get to the configuration-page?
Log in as a super-administrator and go to any Admin-User-Access admin page. Above the tab-navigation, on the left side is a link 'configuration', click that and you are on the configuration page.Upgrade instructions
upgrade instructions pageAdmin-User-Access does not work
Check these things if Admin-User-Access does not appear to be restricting access:
- Check if the plugin is installed and enabled
- Check if the module is installed and enabled
- Check if the module is published to position 'menu'.
In some strange templates the admin-menu-position is a different one then 'menu'. If so, assign the backend-module to the same module-position as the Joomla menu module is assigned to. Or any other position where the toolbar becomes visible. In that case you can ignore the red warnings about the wrong module position on Admin-User-Access admin-pages.
Component access to category and section manager do not seem to work.
Check in Admin-User-Access the component configuration.
Go to config > tab 'component access'
check for categories:
- component-name should be 'com_categories'
- toolbar-link should be 'com_categories§ion=com_content'
check at sections:
- component-name should be 'com_sections'
- toolbar-link should be 'com_sections&scope=content'
save that and go to the 'component access'-page and set the rights again.
empty cache of users browser and try again.
version 2.0.3 > has a workaround for this problem.
Can I set restrictions for users instead of groups?
No. You can assign users to self-created groups. Restrictions can only be applied to these groups and not to individual users.
If you need to set rights for specific users, you can make a group with just 1 user.
Can I use Admin-User-Access for a online demo of the admin?
No!
You can, but I strongly advise you not to do this as its not save. Admin-User-Access restricts access to components-admin-pages, not to their functions. Badly written components can easily be mis-used without admin-page access. So even with this strong access-component there are workarounds for hackers to mess with your site.
Why display articles/modules/plugins greyed out when user has no access?
The thing is, in for example the module-manager, you can select how many rows to display in the module-list. If AUA was to filter those out, there might be 5 accessable modules on the page (the rest is hidden) and there might be more modules the user has access to on the next page (with 20 results), but as there are only 5 shown, the user would not think of clicking in the page-navigation to check the modules on the next page. That is all that is possible without hacking the Joomla core.
That is why the decision was made to gray-out those articles/modules/plugins which users have no access to, instead of completely hiding them
Why do I get a 404 when I log in to the backend
What probably happened is that in the AUA config you selected 'redirect to Pages-and-Items'. Which means that after login at the backend, any user is redirected to component pages-and-items. However, you probably did not install that component, so you configured AUA to redirect to a component that is not installed.
Here is how to fix this:
- log in as a super-admin. You get redirected to the 404 page, but you are still logged in.
- paste this in the url to go to the AUA configuration page administrator/index2.php?option=com_pi_admin_user_access&task=config
- unselect the checkbox at 'redirect to Pages-and-Items'
- click 'save'
404 when click on 'pages-and-items' button
That is because component pages-and-items is not installed. AUA does not need this to function. You can take the button away in the AUA config > tab 'component access'.
End faq
Pre/post sale
Is there a trial version available for testing?
Yes.You can download it on the Admin-User-Access-page. The trial version can be used for a few weeks. When used on localhost there is no time limit. The value of $_SERVER['SERVER_NAME'] should then be 'localhost'.Does the pro-version need Ioncube?
No. The pro version is un-encrypted and does not need Ioncube.Is the pro-version encrypted?
No.free-version pro-version, what is the difference?
With component Admin-User-Access you can manage users:| free | pro | |
|---|---|---|
| article access when editting in backend and frontend | x | |
| category access when editting articles in backend and frontend | x | x |
| sections access when editting articles in backend and frontend | x | |
| page access when editting articles in backend and frontend | x | x |
| itemtype access with component Pages-and-Items | x | |
| component access at backend | x | x |
| module access at backend | x | |
| plugin access at backend | x | |
| workflow settings for Joomla article manager, module manager, plugin manager and component Pages-and-Items | x | |
| Admin-User-Access backend toolbar | x | x |
| custom toolbar buttons per usergroup in the backend | x | x |
| hide Joomla toolbar | x | x |
| auto assign new users to a usergroup | 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
What are the system requirements?
- Joomla 1.5.x fully and correct installed
- No restrictions in the number of posts (read more)
- PHP 5 or later
Not all of the restriction/configuration-settings are saved?
You saved restriction-settings or the configuration-page, but not all settings are saved.
This happens when you have a PHP-plugin on the server which limits the number of post-variables being parsed. For example, there are 60 input fields on a page, but it only parses 50. So some fields get saved, others are not. A PHP-plugin known to cause this behaviour is 'suhosin'.
How to check if you have this plugin:
- login as a super administrator on the backend of your site
- go to 'help' >'system info' > 'PHP information'
- Search for 'suhosin'
Solution:
Disable this plugin or change settings so it allows large numbers of post-variables.
Changed parameters in suhosin.ini to:
suhosin.post.max_vars = 300 (default 200)
suhosin.request.max_vars = 300 (default 200)
What might also work is to set:
SecFilterEngine Off
SecFilterScanPOST Off
in .htaccess
In Joomla 1.0.x there are no component-links in the Joomla-menu or access for admin-usergroup 'manager' and 'administrator' to some components. How to solve that?
The links to the components you can make in the Admin-User-Access toolbar.
In joomla 1.0.x admin-usergroups 'manager' and 'administrator' have no access to some components. You need to take the acl-code out to make these components accessable for these usergroups. Here is how.
- Open in your editor: administrator/components/com_component-name/admin.component-name.php
- Find code like this:
// ensure user has access to this function
if (!($acl->acl_check( 'administration', 'edit', 'users', $my->usertype, 'components', 'all' )
| $acl->acl_check( 'administration', 'edit', 'users', $my->usertype, 'components', 'com_weblinks' ))) {
mosRedirect( 'index2.php', _NOT_AUTH );
} - Comment out this code or just put 2 slashes in front of mosRedirect like this:
//mosRedirect( 'index2.php', _NOT_AUTH ); - Save the file. You're done.