Maybe I'm just not getting the concept of tac_lite, but I can't seem to make it do my bidding.

I'm writing a module for forecasters to post an advisory. The forecaster role should be able to post an advisory only for their region. So, I created the users, the "forecaster" role and the category "regions" w/5 terms. Under access control by taxonomy, I created 2 schemes... read (view), write (update, delete). Anyone can view all regions but only certain forecasters can write for each region.

In the access control for user "freddy" I specify write for only one region, but when I go to create an advisory with that user, all the regions show up.

It's probably just a misconfiguration on my part, so maybe someone can help.

Comments

Dave Cohen’s picture

Dave Cohen commented
Status: Active » Closed (won't fix)

When choosing from list of taxonomy terms, a user will see any term they have view permission for.

If you want to limit the taxonomy select element to show fewer options, you'll have to write your own module and use hook_form_alter to take some of the options away.

I believe tac_lite is doing the right thing in this case, allowing the user to tag content with any tag they can view.

dezolt384’s picture

dezolt384 commented

same issue, did find solution?

Grayside’s picture

Grayside commented

Our policy on creating nodes of a given term is exactly the same as our policy for updating them. Is the default use case supposed to be that users can create a node they cannot later update? That seems like a corner case to me.