I'm getting ready to try out different taxonomy add-on modules. I read something very helpful in Robert Douglas' new book on Drupal (p.131) that modules that implement node-level access controls tend to conflict with each other. He says do not mix multiple node-access modules. I guess this is one reason why civicspace comes with node privacy by role instead of organic groups. Robert Douglas says the modules that provide access controls are:
organic groups
node privacy by role
taxonomy access control
nodeperm role.
Is this a complete list of node access modules? Is there a way to figure out ahead of time whether 2 node access modules will conflict, or is the quickest way "try it and see if it breaks?"
For now I am assuming that I can add on the other taxonomy modules without conflict. I've spent a lot of time reading the various comments. I'll write a compilation of my findings after I've had a chance to synthesize the various comments .
Your input appreciated.
Thank you,
ae2005
Comments
Summary of findings
Here I will put a summary of what I find and comments people add here so that the reader can find a summary quickly without scrolling through every comment.
ae2005
can install if disable another?
P.S. I am assuming that I can install Organic Groups and disable Node Privacy by Role. (I have a test site.) I'm assuming it's okay to install modules that conflict as long as only one is enabled. I'm assuming that I can go back and forth between the two, and see which one fits my needs better before I pick one to choose on my site.
If I'm wrong please let me know.
ae2005
Experimental node access module right for you?
Depending how dangerously you want to live, there is a node access module that allows other access modules to operate together. I am running taxonomy access, simple access, and the core node access permissions together and I can use this experimental module to modify how they interact. So far so good.
It might not be a great solution (I'm not sure of the performance costs or other problems). Check out the discussion and the module if you want:
http://drupal.org/node/23193
thank you
Chad, thank you for pointing out the interesting threads. It's too dangerous for me but I look forward to following up with it going forward. ae2005
Correct
None of the modules should conflict with each other at the database level, meaning you can safely try them out, deactivate them etc. Just one note on that, however. Each of these modules has the prerequisite that the "allow everything" row from the user_access table is deleted for them to be activated, and some (og) put it back in when you de-activate the module. You should probably skip any of the de-activation steps that these modules advocate because you don't want them continuously turning node level access on and off again.
I'll be interested to see what you find. The conflicts can be subtle and non obvious (and there may not be any!). The warnings in the book are just that; warnings. It isn't a given that any of these modules will directly conflict, but a solution to the potential problem isn't addressed in the fundamental design of the mechanism.
- Robert Douglass
-----
My Drupal book: Building Online Communities with Drupal, phpBB and WordPress
thank you
Robert,
thank you very much for letting me know that the database will be okay. I'll post here when I have a summary. thank you for your thoughts.
ae2005
summary 1. Taxonomy Access
there are 13 addon modules that start with the word taxonomy for version 4.6. taxonomy_menu is included with civicspace.
I'll abbreviate Taxonomy as tx sometimes. I'm also including some bugs. The number is the node number that describes the problem.
1. Taxonomy access
http://drupal.org/project/issues/taxonomy_access
**not working with taxonomy dhtml
http://drupal.org/node/18576 March05, 42532 Dec05
**polls double count 26572
**forum bug 41854 Dec05
**access is by last term only 30706,41654
**not working with node privacy by role,22600
**messed up site even after disabling. had to reinstall 20210
summary: this seems like a module with many potential problems. not recommended for beginners.
ae2005
free tag: usefulcomments, usefulcommentsae
why the free tag? see
http://drupal.org/node/43452#comment-81080
4. Taxonomy browser
2. Taxonomy assoc
3. Taxonomy block
creates a block of recent posts by taxonomy term
4. Taxonomy browser
http://drupal.org/project/issues/taxonomy_browser
by Moshe, Oct03
creates a page of nodes related to a certain topic
41802 may only work with version 4.6.3 not 4.6.5 (41499 also)
36149 conflicts with taxonomy access. patch (needs review)
18665 conflicts with postgreSQL
5. Taxonomy context
http://drupal.org/project/taxonomy_context
by Nedjo Jan04
Describes current section and displays breadcrumb trail
43428 trail defaults to lowest vocabulary
summary: seems fairly robust except for 43428
this is the module recommend by Jaza (Jeremy Epstein) in his approach to breadcrumbs.
moved
moved
6. Taxonomy dhtml
http://drupal.org/project/issues/taxonomy_dhtml
lists recent nodes on your site by taxonomy
provides node counts by vocabulary
**conflicts with taxonomy access control, 42531
**summary: taxonomy access control seems to be mentioned more often, but this module is mentioned fairly often
7. taxonomy hide
hide some terms
8. taxonomy image
associate images with taxonomy
9. taxonomy import
via XML
10. Taxonomy menu
allows you to add taxonomy terms to the global navigation menu
taxonomy menu is included with civicspace
this is a pretty stable module
**links to a tutorial on taxonomy menu
http://drupal.org/node/43507#comment-80918
This tutorial is for Drupal 4.5+. I have not succeeded in getting it to work with 4.6 but I guess I did something wrong.
11. Taxonomy multi-editor
http://drupal.org/node/11869
http://drupal.org/project/issues/taxonomy_multi_edit
edit taxonomy terms on one page
by moshe
few bugs
**limited to 200 terms by design
12. Taxonomy theme
choose a theme by taxonomy
13. Taxonomy ticker
provide news in ticker style by taxonomy
how
php block 44325
problems
49715 problem caused by taxonomy access and solution
39053 what taxonomy context does not do
devel and organic groups seem to conflict if you have more than 1 administrator. loses access to admin functions