I understand how your module is different from Taxonomy Access Control and Taxonomy Access Control Lite in that these aim to restrict access to nodes based on taxonomy terms/vocabularies per role and per user. Your module controls access to vocabularies per role (perhaps sometime it will support per user as well).
Would you consider to join forces with Vocabulary Access Control, since you already have insight in one of this module's goals? Joining forces also means joining audience, which in turn will bring more testers and will help the advance of the module in general.
PS: I know that the module seems relatively inactive, but it does look promising.
Comments
Comment #1
jcisio commentedThe Vocabulary Access Control seems inactive, and has only about 20 active users. So I think I'll let that module owner decide.
Comment #2
klonosFair enough! ...switching to that module's queue then.
In the meantime, it doesn't hurt to 'borrow' some ideas from its code and UI ;)
Comment #3
klonos+ a link to Vocabulary Permissions so people don't have to search for it ;)
Comment #4
klonos...forgot status change.
Comment #5
sgabe commentedIt seems the only part of VAC which is working good is already covered by VP. The node access part of VAC definitely needs work and can't be used in the current state. Sorry, but due the lack of time and interest I couldn't finish this module. Now I'm not sure if it's even needed at all. If someone is interested or has an idea don't hesitate to contact me.
Comment #6
klonosThanx for taking the time to reply Gabor.
Could you please update the module's page with that info so that people know about this fact. Perhaps open an issue for taking over the module + provide the link to that issue in the module's page too. Than you once again.