JUGA - Joomla User Group Access




JUGA is NOT A HACK and it is NOT ENCODED.
JUGA installs and uninstalls *easily* as a component. To activate/de-activate it, just install and publish/unpublish the JUGA Plugin/Mambot. And we believe in leaving our source code open, so you can modify JUGA as you wish.
With JUGA, you can assign users to multiple groups. In fact, you can create an infinite number of new groups, so you could assign a single user to a unique group, thereby achieving customized individual access rights for each user.
After installing JUGA, merely synchronize it with your site's components and content. Then tell JUGA which variables it should restrict for each component (in the case of Fireboard, for example, you would tell JUGA: "func", "catid", "task", "id", etc). Then, define which items each group has access to. After assigning users to JUGA groups, activate the Plugin/Mambot and voila! It works the exact same way for your back-end.
We have released a modified version of the Joomla! Main Menu Module. It has been modified to work with JUGA>>Groups and hides menu items from view when a user doesn't have access to them.
We also have a JUGA Content Plugin/Mambot. Now you can show certain portions of a content item to any/none/some/all JUGA>>Groups. It works like JHide and RokAccess.
We also have an admin-side template for Joomla! 1.0 that extends JUGA's controls over your J!1.0 Admin Control Panel. This template isn't necessary for J!1.5 as the JUGA System Plugin will already control the admin-side for you.
Finally, we also have mod_hiddenbyjuga, a JUGA Module that allows you to HIDE MODULES based on the user's JUGA Group!
- This extension requires registration to download.
Way to goes guys, you really set the bar for the rest of the developers.
I like the fact that Juga is not a hack. If you get it all terribly wrong and lock yourself out, there is a way to put things right.
In order to get the best out of the product, you will have to take time to understand how Juga works. To begin, Juga is about taking a standard Joomla user group and restricting its permissions, not granting them. If you want a user to only edit one article, you must make them a Joomla Editor but then restrict editing rights to all but that one article.
Second, Juga works on URL strings that they call Site Items. In the example above, you would find the editing URL for the article (on the front and/or admin side) and give permissions to the Juga group your user was a member of. Since their group would not be assigned to edit any other articles, they would not have any access.
I have found the component very useful when it comes to creating multiple secure areas on a single site. Each secure area is for a separate audience, with separate content for each and never the twain should meet. I found that Joomla's broad usergroups does not support this approach. One registered user area is the same as another. With Juga and its dynamic menu module and a module to hide other modules, depending on user group, I have solved this problem.
All in all, a very good component that was worth paying for.
I bought it because of that and it seems like it can´t do anything for me, so the rating is correct based on my goals. Two questions to the support just brought me short answers pointing out what´s "not" working. A one-liner with a link to the manual (that I didn´t find before) showed me, that JUGA will never work for me.
So what´s about it? JUGA may be great to limit access to Backend-Users. To adjust the rights for Components and so on. But it has no value for me on the front end.
What I was searching for was a component where I can give rights to the front-end-users so they can submit articles. Thes was the onlies real thing I needet and this is how I understood JUGA: Give my Front-End-Users the rights to create articles. But ... no way!
I can´t give without touching each and every user by hand. I have at least to take him into an JUGA-Usergroup, and this can´t be done in a batch, with a search or whatever, I have to do this for each and every single user.
But still, when I do it, the access to writing articles is not working. Because in the Front End he is still a "User" and a User can´t access to the "submit-article-things". So I also would have to change all "Users" to "Authors".
In Fact, JUGA could be a great component to manage the rights between different Admins. And if this would be described will it would have been fair. But in fact, let´s face the main line that JUGA is described with on theire own website:
"JUGA is a Joomla Extension that allows additional control over what content is available to which users."
That´s not right. It is worthless if you want to handle access for users. It´s for Administrators.
This review isn't actually a review of JUGA -- this review is a criticism of com_content's requirement that a user be at least an "Author" in the Joomla ACL before they can submit an article.
As the writer says: "What I was searching for was a component where I can give rights to the front-end-users so they can submit articles." He then continues to relay the message that we had given to him in a support ticket -- that Joomla requires a user to be at least an Author in the Joomla ACL before they can submit an article.
His frustration and criticism has nothing to do with JUGA, but rather with com_content's requirements.
JUGA doesn't hack the J1.5 menu structure. We provide a separate module (called mod_mainmenujuga) that you can use to display your menus should you choose, and to create the menu you use the same admin-side Menu Manager that you would for mod_mainmenu.
Configuration can be very quick -- assuming you follow the manual...
Some templates use their own internal module for displaying menus -- this is not something we can control (nor do we want to).
In these cases, to make the module recognize JUGA's restrictions, you will have to modify the template's internal module.
Their support is amazing and the extension works as promised.
Support is second to none and the $50 I paid was worth every penny. Response is lightning fast, and when I asked about adding functionality I needed for a special job, they added it, sent me a patch and rolled it into the core product all with 24 hours!
The support I received was above and beyond anything I've received from any component/module developer to date.
Gives me more than enough confidence to highly recommend my clients and others to use Dioscouri components.
when i run this particular Component , it hangs and it takes at least 10 minets for items Tobe loaded
its performance is very poor
They diagnosed my problem - a missing file that was mistakenly deleted by a developer and installed it - JUGA works great now.
I had a minor issue, that was quickly solved after filing a support query. I was worried about it working with MyBlog after reading cryptic comments on some forums, but all seems fine.
The online documentation is comprehensive, if slightly disorganised. You can return to your previous settings by uninstalling, if necessary.
1. Hiding/Showing menu links does not always work well depending on your template menu system. (e.g. if you are using/modifying templates from joomlart or yootheme, you may find things not as straightforward as juga suggest.
2. Search - we found that you could hide/show content easily enough based on user groups, but that content can still be found if you search for it. Which kind of defeats the purpose.
3. Links to Sections/Categories - If you are displaying a list of links e.g with a section list those articles that you have set to be hidden will still show.
4. It is recommended that you only 'synchronize' your content with JUGA when you first install, but we found that site items did not always show up.
Overall we like this component and feel the developers have done a good job and addressing something that we will all find useful.
We are sticking with it and will use it again. We recommend it.
At first, I thought I'd wasted my precious money, but now feel that it's worth it.
I did run into a bug, where 11 particular site items were self-replicating themselves when a Joomla Administrator user was logged into the admin-side, and publishing content items. The folks at Dioscouri were very helpful. My paid support subscription was well worth it. Their responses were very open-minded, and quick. by listening to the problem, they were able to determine a small bug in the 1.0 version of JUGA, and immediate posted a patch to their site.
Great work! My sites wouldn't be the same without JUGA.
I got quick response and they took the time to personally help me configure JUGA so that users that I assign to groups have access to selected UHP2 sites, and not others.
First class extension, first class support, first class company.













