| Attribute | Average |
|---|---|
| Features | 3.2 / 5 |
| Reliability | 3.2 / 5 |
| Ease Of Use | 2.8 / 5 |
| Documentation | 3 / 5 |
| Vote Count | 5 |
Access control for user roles based on taxonomy categories (vocabulary, terms). Automatically controls access to nodes (based on their taxonomy terms) Configuration page for each user roles Five permission types (View, Update, Delete, Create, List) (If you want Taxonomy Access Control for individual... [More...]
| Maintainer: | keve |
| Links: | |
| Categories: | Security, Taxonomy, User access and authentication |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 6.x-1.2 | 2010-Mar-18 | Download | Recommended |
| 5.x-2.0 | 2010-Mar-09 | Download | Recommended |
| 6.x-1.x-dev | 2010-Mar-19 | Download | Development |
| 5.x-2.x-dev | 2010-Mar-10 | Download | Development |
Options: Add a review
This module is difficult to configure and a bit un-intuitive to administer (RTFM!), but it adds powerful, fine-grained control and flexibility to Drupal's access control.
Use case that other access control modules can't cover: Various groups of users can add and update content in certain categories of a content type, but should not have permissions to add or update everything in a content type. In my case, I have a few content administrators for each department; these content administrators can post documents and announcements in various taxonomy categories, and update documents or or announcements that have already been posted in those categories, without having this sort of access for taxonomy terms belonging to other departments.
Edit: increasing my score for "reliability" because the next release will have the major bugs fixed. (I know, because I fixed them!) The documentation should be a bit better now, too.
If you have a very simple site, this module will likely work for you. If you are managing a large array of users, content types, and permissions, then this module is definitely not for you. It tends to be confusing as to why certain permissions are triggered and when. It also tends to screw with the drupal API in weird ways - so if you are running lots of other modules, they may end up interacting with TAC in funky methods. TAC costs me lots of lost time because it was overriding a node_save that another module was calling.
The writers and maintainers of this module deserve a lot of credit.
I have used it in 4.6, 4.7 and 5.7 and it certainly does work. But it is hard to get your head around sometimes how it works and the practical effect of different settings.
I think the difficulty is inherent in having to bolt something fundamental onto Drupal core alongside the core role and access permission systems. Imho it illustrates the need for a much more granular approach to content access being built into core.
The documentation is reasonably clear in the context of the above.
When I first set my site up 3 years ago I was pushed towards Organic Groups, didn't feel that gave me the user experience I wanted, tried simple_access but found it was TAC that really provided me the functionality I wanted.
From my own experience, it is worth looking at more than one module to see which most closely matches what you want to do. And the only problem with that is you don't really see the possible pitfalls until you have installed them and tried to run with them. A comprehensive and comparative review of the different node access modules would be useful.....
This is a must have module if you are building a content driven website
For my purposes, these modules were useless. Tac_Lite and Taxonomy Access Control utterly failed to provide role-based access to taxonomies.
I've tried the arcane, and mislabeled, "create" toggle. I've tried the "rebuild permissions" button. Perhaps I don't really understand what these modules are for, but if you're trying to apply vocabularies based on user role, look elsewhere.
Documentation for these mods is also spotty.
"The issues raised in shl's review have been addressed in versions 1.7 and above. I can't add this comment..."
"This module will make the Upload Files Form beautiful. It doesn't work with filefield, just the upload..."
"despite a nice interface, the permissions are not copied but Duplicate Role works - http://drupal.org/project/duplicate_role "
