FAQs Frontend-User-Access

Installation

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.

End faq

   

Configuration

I'm hiding a module but the module-title still shows.

You are probably using a 3rd party template which uses a module-override which is not parsing the module css-class-suffix properly. Templates by YOOtheme and some Artiseer templates seem to have this issue.

In case you are wondering if this is a template issue, set your site-template to Joomla's default 'rhuk_milkyway' and check if modules are hidden.

What some templates do wrong is that they often totally ignore the css-class-suffix as set in the module configuration (try it!). To make Frontend-User-Access hide modules, this must be fixed in your template.

read more

show/hide menu-items and menus

FUA can hide individual menu-items, using the menu/page access restrictions together with the FUA menu-module. The menu-module is an altered clone of Joomla's mod_mainmenu.

If you want to use another menu-module AND hide menu-items as set in FUA, read more.

To hide the whole menu, use module access restrictions.

How do I get to the configuration-page?

Log in as a super-administrator and go to any Frontend-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.

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.

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

How to update?

Please carefully read the update instructions

Where to edit the 'no access' messages?

In the FUA configuration you can edit the messages for the different access restrictions.

Will users not connected to a usergroup have access?

Yes and no, depending on your configuration. In the default install is a usergroup called 'logged in'. Which are all logged in users not assigned to any usergroup. You can set any access-restrictions to that group, just lke any other group.

Yootheme-templates break HTML when hiding articles

In Yootheme-templates, when hiding an article on a blog-page, the HTML could break and the page will show wrong. This is because FUA uses the Joomla plugin-event 'afterDisplayContent', which is suppose to be loaded after the content is displayed. Yootheme does not load the event after the content is displayed, so the html breaks.

Here is how to fix that:
files:
templates/yootheme_template_name/html/com_content/section/blog_item.php
AND
templates/yootheme_template_name/html/com_content/category/blog_item.php
line: 142

<?php echo $this->item->event->afterDisplayContent;         ?>
</div>
</div>

change to

</div>
</div>
<?php echo $this->item->event->afterDisplayContent;         ?>

So the 'afterDisplayContent' is actually loaded after the content is displayed.

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. The pro version is un-encrypted and does not need Ioncube.

Is there a trial-version available?

Yes. You can download the trial-version on the project page. You can use this extension unlimited on localhost. If used online it can be used for a few weeks.

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

With Frontend-User-Access you can set frontend access restrictions to:
free pro
menu-item/page access
x
components x x
modules (hide modules when user has no access) x
articles (specific articles)(hide article when user has no access) x x
articles by category x
articles by section x
auto assign new users to a usergroup x
redirect users after login
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
  • Cache needs to be disabled in Joomla global configration

Your server might be configured to limit the number of posts

On your server might be a PHP plugin which restricts the number of posts that can be made when saving access data.  Read more.

3rd party templates

Some 3rd party templates use a module-override with ignores the css-class-suffix as set in the module configuration. Read more.

Conflict in Docman

There is a conflict with Docman. When module-access restrictions are activated, users can't upload files from the frontend. We spend days trying to make a workaround for this, unfortunately without any result. We hope that when Docman migrates to the MVC-model the conflict will be solved. Until then we recomment you use one of the many other free download-extensions, like Phoca download. Or you can use the option in the FUA configuration > tab 'module access' to disable the module-restrictions for that particular Docman-upload-page.

Wordpress component access restrictions do not work ?

Component com_wpadmin by CorePHP is a component for frontend editting of wordpress intergrated in Joomla. For some reason this component does not load the system event 'onAfterRender' which is required for Frontend-User-Access to restrict access.

Here is how to fix this issue.

file:
/components/com_wpadmin/wpadmin.php

line 19:
Code:
if(!defined('WP_JPATH_ROOT'))
define('WP_JPATH_ROOT', JPATH_ROOT . '/components/com_wordpress');


replace with:
Code:
if(!defined('WP_JPATH_ROOT'))
define('WP_JPATH_ROOT', JPATH_ROOT . '/components/com_wordpress');

//load system event onAfterRender
JPluginHelper::importPlugin( 'system' );
$dispatcher    =& JDispatcher::getInstance();
$results = $dispatcher->trigger('onAfterRender', array ());

End faq

   

SEO by AceSEF