Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi everyone!
I am using Tac_Lite to control access to my nodes.
Regular nodes are working well with Tac_Lite (http://drupal.org/project/tac_lite), but Storm nodes are not.
If taxonomy term does not allow user to see a node, it does not appear in corresponding list (like Organizations, etc), but the node itself _is_ accessible through direct link ....node/10
Can this problem be solved? It prevents using such a good tool!
Comments
Comment #1
Magnity commentedStorm implements its own access functions in order for the Storm permissions to override Drupal node permissions. However, obviously we don't want to expose these nodes unnecessarily if there is a way for the modules to work together.
Moving this to Tac_lite - hoping that the maintainer there can see if there is a quick fix / give a few pointers that will enable these Storm to be compatible with Tac_lite (i'm not familiar with Tac_lite).
Tac_lite maintainer: please feel free to move the issue back to Storm once you've had a look at this - even if there is no ready solution. Thanks.
Comment #2
Dave Cohen commentedIn drupal today there's no easy way to customize the logic of two node_access modules.
#309007: Add drupal_alter() after hook_node_access_records() will improve things. Although who knows if it will be back-ported to D6.
Comment #3
Magnity commentedThanks @Dave Cohen.
Hence, i'm putting a won't (can't) fix - by design Storm has specific access control for its nodes, so it looks like we can't have both at the moment.
@mpohoril: I you want to have tac_lite working, you'll need to customise your Storm installation to remove the node_access fuctions.
Comment #4
Magnity commentedNB: Storm documentation has been updated to mention this conflict.
Comment #5
Dave Cohen commentedHey Storm looks interesting. I'll check it out when I get a chance. Glad to know about it.
Just want to mention that you could follow the Organic Groups approach. In that module, all the node_access code is in a seperate module, og_access.module, so it can be enabled or disabled as needed.