| Attribute | Average |
|---|---|
| Features | 4 / 5 |
| Reliability | 4.5 / 5 |
| Ease Of Use | 3.75 / 5 |
| Documentation | 4 / 5 |
| Vote Count | 4 |
This module restricts access so that some users may view content that is hidden from others. A simple scheme based on taxonomy, roles and users controls which content is hidden. As the name implies, this module shares some functionality with an earlier module called Taxonomy Access Control (TAC). If... [More...]
| Maintainer: | Dave Cohen |
| Links: | |
| Categories: | Security, Taxonomy, User access and authentication |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 6.x-1.3 | 2009-Mar-20 | Download | Recommended |
| 5.x-1.3 | 2008-Sep-17 | Download | Recommended |
| 6.x-1.x-dev | 2009-Apr-18 | Download | Development |
| 5.x-1.x-dev | 2008-Jun-26 | Download | Development |
Options: Add a review
Went through the gauntlet of taxonomy based access control modules, and this one won the battle today. I needed both role and user based permissions, and I liked the way that I can control per user taxonomy access on the user as opposed to the term, which is what some of the other modules were trying to do.
My usecase:
I installed a calendar for events which are tagged public, internal, private within a special taxonomy for an event content type in cck (+ date + calendar)
My aim was to show the private dates only to the client, the internal events to ppl with the role "supporter" and the client, and the public dates to everyone.
With this module, everything i planned was carried out in a matter of 2 minutes.
All dates are displayed according to the settings in the calendar und the upcomming events block.
Simply perfect!
its difficult to say any drupal node_access module is straightforward and easy to understand, but this module is the best that I have encountered. for simple audience controls, this is the module I go to.
There is one thing you should know before using this module, which may be not so obvious and is not explicitly documented: the access is granted by union, not intersection.
So, for example, when you have a node tagged with two terms and one term is given access for a certain role and the other is not - you will get access to that node. Even though the taxonomy term will be hidden.
"There was a problem with Image Caption and a theme that I made in artisteer. It should work with most..."
"I'm not sure if I could have built my website without this. I used to use the yui editor, but it had..."
"I think that this module is great. It was easy to utilize vertical tabs in my module. If you want to..."
