Installation / update

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/content/
• 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.

How to update?

1. Download the component.
   free- and trial-version
   pro-version
2. Install the component over the old component (no need to uninstall first).
3. Install module Admin-User-Access (backend) over the old module (no need to uninstall first).
4. Install the system-plugin over the old plugin (no need to uninstall first).
5. Install the user-plugin over the old plugin (no need to uninstall first).

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 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.

If you are updating from any component version lower then 2.0.4, please carefully read the update instructions.

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 versions over the old versions.

Admin-User-Access for Joomla 1.6/1.7?

Admin-User-Access will NOT be released for Joomla 1.6/1.7.

Joomla 1.6/1.7 has almost all of the ACL functionality integrated in the core, so there really is no point.

Error 'Content Encoding Error' when system plugin is enabled

In the Global configuration > 'server' disable 'GZIP Page Compression'.
We are currently not sure why the system plugin has anything to do with this compression and are working towards a solution.

End faq

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'.

Backend restrictions do not work. Admin-User-Access does not work with my administrator template. Toolbar does not show.

The AUA backend module needs to be enabled and 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 'administrator' 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. If that position is different then position 'menu' and it then works in your template, you can ignore the warning-messages on the admin-pages about the wrong module-position.

RocketTheme missioncontrol-template

This admin-template almost completely ignores the module positions, so you will have to assign the Admin-User-Access backend module to position 'header' and add a line to the template so it actually loads the module.

file:
administrator/templates/rt_missioncontrol_j15/index.php
line: 52

<jdoc:include type="message" />

replace with

<jdoc:include type="modules" name="header" />
<jdoc:include type="message" />

Then ignore the warnings in AUA about the module 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.

How do I get to the configuration-page?

Upgrade instructions

Admin-User-Access does not work

First consider what is not working.
Then read on at:

• backend restrictions are not working
• frontend restrictions are not working

Component access to category and section manager do not seem to work (version 2.0.3 and lower)

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&section=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.

For the module-manager there is a workaround:
If you don't want your administrators to see all those greyed out modules, you can create buttons to those modules in the AUA toolbar. The administrator can then go straight to a specific module, edit it and when saving the administrator can get redirected to the url specified in the AUA config > tab 'module access'. So the administrator will never get to see the greyed out module list in the module manager, and still be able to edit the modules he/she has access to.

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:

1. log in as a super-admin. You get redirected to the 404 page, but you are still logged in.
2. paste this in the url to go to the AUA configuration page administrator/index.php?option=com_pi_admin_user_access&task=config
3. unselect the checkbox at 'redirect to Pages-and-Items'
4. 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'.

Frontend restrictions do not work (version 2.2.0 and lower)

Please make sure the Admin-User-Access frontend module is assigned to a module position which is loaded on the article-edit page. To make sure, go to the article edit page and check which module is already on that page. Then go to the module manager and find that module (disable/enable it so see if you got the right one). Check the module's position. Then assign the Admin-User-Access frontend module to that same position.

Edit buttons are still shown at the frontend at each article when user has no edit-access

We are sorry to say that Admin-User-Access can not hide those edit buttons the user has no edit-access to. Joomla does not give these buttons an id or classname, so they can not be identified to be hidden.

Where to edit the 'no access' messages?

Depends if the message is frontend or backend. Assuming you use english:
backend:
administrator/components/com_pi_admin_user_access/language/english.php
frontend:
language/en-GB/en-GB.com_pi_admin_user_access.ini

Where do I start? I don't understand how to start configuring this.

1. create a usergroup
2. assign a administrator-user to the group
3. go to the AUA config and enable 'module access' restrictions
4. get out of the config to the 'module access'-page and give the group access to some modules
5. logout
6. login as the administrator-user
7. go to the module-manager
   note that the user can not edit the modules the user has no access to.

That is the basics for one restriction-type. Slowly build up the access, one restriction-type at a time, testing each type before moving on. It is quite easy to just tick some boxes in the configuration and restrict too much, so build up restrictions slowly.

Using the YooTheme Enterprise template the frontend module displays as an empty rectangle and part if page is visible when a user is restricted from editting content at the frontent of the site.

When using the YooTheme Enterprise template, assign the AUA frontend module to position 'absolute'.

Articles edit from frontend per user ? Edit archived articles from frontend?

To display a list of articles per user, or to display a list of archived articles for editting, use Frontend-User-Article-List:
http://extensions.joomla.org/extensions/news-production/content-submission/8656

Hide menutypes in the Joomla toolbar in the backend

As of version 2.4.0, menu-type restrictions can be set. But to hide the menu's in the Joomla toolbar itself, this caan not be achieved without altering a core file. We do not encourage you to do this because when updating your Joomla version, this will be overwritten and chances are, you will have forgotten all about it. But if you really must hide those menus in the toolbar, this is how:

file:
administrator/modules/mod_menu/helper.php

line 95

if (count($menuTypes)) {

replace with

$database = JFactory::getDBO();    
        
        //get menu access data
        $database->setQuery("SELECT menu_groupid FROM #__pi_aua_menus ");
        $menutype_access_rights = $database->loadResultArray();    
        
        //get user id
        $user = JFactory::getUser();
        $user_id = $user->get('id');
        
        //get usergroup
        $database->setQuery("SELECT group_id FROM #__pi_aua_userindex WHERE user_id='$user_id' LIMIT 1 ");        
        $rows = $database->loadObjectList();
        $aua_usergroup = '';
        foreach($rows as $row){
            $aua_usergroup = $row->group_id;
        }        
        
        //make menutype access array
        $menutype_access_array = array();
        for($n = 0; $n < count($menutype_access_rights); $n++){
            $menu_type_right = $menutype_access_rights[$n];
            $temp = explode('__', $menu_type_right);
            $temp_menu_type = $temp[0];
            $temp_groupid = $temp[1];
            if($temp_groupid==$aua_usergroup){
                $menutype_access_array[] = $temp_menu_type;
            }                    
        }
        
        //if user has no access, rip it out of menutype array
        foreach($menuTypes as $key => $temp){
            if(!in_array($temp->id, $menutype_access_array)){                        
                unset($menuTypes[$key]);
            }
        }
        
        if (count($menuTypes)) {

403 error when saving admin page

This error is not generated by Admin-User-Access but by Akeeba.

Please read this forum post.

End faq

Pre/post sale

Is there a trial version available for testing?

Does the pro-version need Ioncube?

Is the pro-version encrypted?

free-version pro-version, what is the difference?

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. 

What is the difference between Frontend-User-Access and Admin-User-Access?

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:

1. login as a super administrator on the backend of your site
2. go to 'help' >'system info' > 'PHP information'
3. 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.

1. Open in your editor: administrator/components/com_component-name/admin.component-name.php
2. 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 );
   }
3. Comment out this code or just put 2 slashes in front of mosRedirect like this:
   //mosRedirect( 'index2.php', _NOT_AUTH );
4. Save the file. You're done.

Workflow tab gives blank page when PhocaPDF plugin is enabled

There was a conflict between the Phoca pdf plugin and Admin-User-Access' workflow page.

To fix this, download a fresh version of the Phoca pdf plugin, this will resolve the conflict.

End faq