Closed (won't fix)
Project:
Taxonomy Access Control Lite
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Aug 2008 at 04:17 UTC
Updated:
25 Sep 2008 at 19:37 UTC
Comments
Comment #1
Dave Cohen commentedCan you be more specific?
I'm no expert in OG, but I see no reason for either module to cause a problem with the other. OG has its own access control module which I have no experience with.
Comment #2
pengi commentedI got that impression from the og docs page (http://drupal.org/handbook/modules/og) where is says: "You cannot use this module with other node access modules."
The link is to http://drupal.org/node/23193
Comment #3
Dave Cohen commentedIt's not a problem with tac_lite. It's either a problem with Drupal's access_control in general, or og's access control.
It may be that they could work together, but only if the administrator really knows what he/she is doing and makes no mistakes. Either way, I don't see this as something that tac_lite can fix. Unless you have a specific suggestion of what needs to change.
Comment #4
pengi commentedRight, I didn't think it was a problem with tac_lite per se. I just wanted to verify that tac_lite wouldn't be likely to work with og. I've never used og or tac_lite or tac so it's not something I have experience with from any angle. However it's important to know if implementing og will mean that these access control tools won't be options.
So I guess you concur that they can't be expected to work together, as implemented by a casual drupal user. Too bad.
Comment #5
Dave Cohen commentedDon't take my word for it. I have no idea why someone wrote: "You cannot use this module with other node access modules." I think you should be asking the og_access developers.
Comment #6
Grayside commentedOur intention is to leave OG Access universally and permanently set to Not-Public, then use tac_lite to expand viewing access.
The two don't work together in the sense that they are OR'd together, meaning if you do set something to Public, it completely trumps tac_lite.
Comment #7
Dave Cohen commentedThe nature of drupal's access control is that access is denied by default, but if anything grants access, its granted. As you say, its OR logic.
There was a robust discussion about these things at the last drupalcon and some changes that make schemes more flexible should hit in the D7 timeframe. Until then you basically have to write your own access control logic.