How does tac_lite relate to taxonomy_access
voipfc - September 13, 2009 - 13:40
| Project: | Taxonomy Access Control Lite |
| Version: | 6.x-1.3 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
How does tac_lite compare with taxonomy_access?
What does one do that the other does not?
What advantages does one have over the other, can they run together if one is disabled, without losing their settings?
#1
They are two different modules, maintained by different developers. If you want to take some time to compare them and document the differences, great!
If you enable both, there may be problems. Drupal 7 introduces changes that make it easier for two node_access modules with work together. If only one is enabled, there should be no problems.
#2
IMVHO, this module's name is misleading.
I spent several *weeks* trying to make Taxonomy Access Control and Content Access to play well together in D6. My setup had very specific needs which were not complex and that I could easily define. But I simply couldn't get it to work. It was a seemingly unsolvable four-dimensional logical nightmare.
The only reason I didn't try "Lite" first was because of the module's name. To me, and I suppose to other people as well, "Lite" immediately implies "less features". I was too busy wrestling with TAC – and probably too stupid as well – and therefore haven't read Lite's documentation throughly enough to see that these modules have *nothing* in common, except the first three words in their names...
TAC and TAC Lite are both excellent modules. In my specific case, I could only achieve what I needed with TAC Lite. It's not less powerful, it's just different.
Both are easy to setup if you know what you're doing, but they approach taxonomy permissions from different angles. Hence my adoption of TAC Lite instead.
YMMV.
#3
Historically, TAC came first. tac_lite came after Drupal core introduced the node_access table. This made it possible to do more with less code, especially without concern for supporting older features. tac_lite is a smaller amount of code and more lightweight. It still introduces no new database tables, for example. It has grown some new features over time. And its great to hear this report of success. But I'm not inclined to change the name, should I?
#4
As the module's developer, the module's name is obviously your call. I was just pointing out what the word "Lite" implies, in my opinion. It's not a major deal, for me at least, since I finally found your module... :)