when a user adds a term in the vocab configured for TAC_Lite, the term is added successfully but the user is not automatically granted view/update/delete to the term so (s)he is unable to see the added term. For my site, the user needs to immediately be granted view/update/date for his/her added term. If this is not a feature to add to the module, is there perhaps a quick fix/hack to do this I might try? Perhaps a rule "when term Y of vocab X is added, execute PHP code that would grant scheme 1 to the acting user for term Y." Any hints on what that might look like more specifically or if it is even a good idea?

Thx,

-John

Comments

whyameye’s picture

BTW for my purposes it would work just as well if I could specify that TAC_Lite should administer restricted permissions only for the root level of the vocab.

Dave Cohen’s picture

To me this sounds like the module could use hook_form_alter to change the add (and edit) taxonomy term form. And in that form add the necessary privacy options. This sounds like a great idea and worth including in the module.

I don't have time to address this right now, and probably would not have time for several weeks. So, any volunteers?

whyameye’s picture

looking deeper at the functionality I am looking for, I don't actually think this will help me. What I really wanted to do is allow different roles different privileges for administering branches of a vocabulary. For example, users with role "Cadence" could perhaps create/edit/rename/delete all children in a hierarchical vocabulary under a branch term also called "Cadence." They would not be able to administer under nodes of sibling branches to Cadence.

I could do the "add children under Cadence" and "associate nodes with children under Cadence" with TAC_Lite perhaps, but then there is no way to give my users the ability to rename, delete etc. these children without just giving them "administer taxonomy" and once I do that they have access to all taxonomies so my plan is foiled.

The only solutions I can find in Drupal to my problem with preexisting modules is to use Organic Groups/OG_Vocab or Taxonomy Delegate. With either solution I would have to assign administrative taxonomy rights to users by entire vocab instead of a branch in a vocab. However I do it seems a bit clumsy and ugly. I think users will find both solutions unintuitive without massive tweaking on my side. Oh well.

Thanks for getting back to me on this.

-John

Dave Cohen’s picture

Status: Active » Closed (won't fix)

Right, tac_lite is a node access module. Doesn't try to do anything with taxonomy. Sounds like your best bet is to use hook_form_alter to add validation and alter the vocab forms, to prevent users from doing things they're not supposed to.