|
Can JUGA hide Admin-Side Menu Items? |
|
In Joomla! 1.0.x, while using the JUGA-Enabled Admin-Side Template, YES, JUGA will hide menu items to which the logged-in user does not have access.
In Joomla! 1.5.x: NO, JUGA cannot hide menu items on the Admin-Side. This would require a HACK, which we've deliberately tried to avoid.
|
|
Can JUGA Restrict Users to VIEWING one Section/Category? |
|
Yes, JUGA can restrict users to VIEWING a single section/category.
|
|
YES! Copeland posted a great step-by-step in our forum, but for ease of use's sake, we're copying the content here... (original link: http://www.dioscouri.com/forum/func,view/catid,6/id,1530/ )
-
Get AEC and JUGA installed.
- Setup JUGA (using the Dioscouri manual or glassman's brilliant post in the tips and tricks forum)
- In the AEC --> Settings page in the backend, click the micro integration tab and make sure JUGA is selected.
- Hit save
- Go to AEC --> Micro Integration and create one using the JUGA plugin
- Hit save
- Re-open the Micro Integration you just made and it will be have an extra tab with all options you can choose from.
- Set it up accordingly
- Create a plan
- Click the Micro Integration Tab when you are done making the plan and choose the micro integration you made...
|
|
What is the "n/a" under Include? |
Many of you have asked why there is an "n/a" under the "Include" column in JUGA>>Site Items. Here's the answer!
- The content articles are "n/a" in the include column because they are
part of the "Content Component". The *com_content component* CAN be
excluded/included from JUGA's restrictions, but for individual content
items, you must assign them to a JUGA group.
|
|
Does JUGA work with com_wrapper? |
|
In Joomla! 1.0.x: No
In Joomla! 1.5.x: YES, but with this method only: http://www.dioscouri.com/forum/func,view/catid,4/id,2224/#2219 (special thanks to Renato for implementing this fix to com_wrapper, something we at Dioscouri believe should be part of the core)
The reason this fix is necessary is that other than the `Itemid` value, com_wrapper URLs are
all identical. JUGA doesn't distinguish between Site Items based on
their `Itemid`, so if the only variance between two menu item links is
their Itemid, then JUGA will treat them as the same link.
In other words, you won't be able to get JUGA to distinguish between
com_wrapper items, and therefore won't be able to assign them to
different groups (unless you're using J! 1.5 and implement Renato's fix).
|
|
Does JUGA work with SEF enabled? |
|
Can I restrict an Admin to only one component? |
Yes, yes you can.
The method for doing this is the exact same as doing it for your front-end components. You will need to
- create the appropriate JUGA Groups for your Admins,
- configure your Admin-Side Site Items so they are assigned to the appropriate JUGA Groups and
- assign users to the relevant JUGA Groups.
Please see our Manual, HowTo, and Troubleshooting
pages for JUGA (in the JUGA section of the "Our Extensions" menu). They
address many of the issues new users may have with configuring JUGA.
|
|
Are JUGA Groups Recognized by aMember? |
|
No, unfortunately JUGA and aMember do not play well together.
|
|
Do I need Zend / IonCube? |
|
No you do not. None of our components are encrypted. You are free to customize them to fit your needs perfectly.
|
|
Can I Use It on More than One Site? |
|
Yes, your license allows you to use it on more than one domain.
|
|
