Resetting taxonomies when used in conjuntion with Tax Access Control
| Project: | Event with volunteer time slots |
| Version: | 5.x-1.0 |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I am using Taxonomy Access control to keep certain roles from using certain taxonomies. There appears to be a conflict with the Volunteer Timeslots module, but I'm not sure which module needs to be fixed. Here's my problem:
1. User A creates an event with volunteer timeslots (Node 1), and tags it with Term A. (only User A has access to use Tag A)
2. User B logs in and views the volunteer timeslot node (Node1) that User A created. (User B cannot see Tag A because he doesn't have access to it)
3. User B checks a timeslot and submits the form for Node 1.
4. Term A is removed from Node 1, apparently because User B submitted without access to this term.
This is a problem for me because I use these taxonomies to filter my events into specific calendars. What is effectively happening here is that unprivileged users are creating changes to taxonomies on a node, thus changing their behavior. Is it possible to prevent Volunteer Timeslots from making any changes to a node other than whatever is associated with storing the timeslot's checked state?
I hope this makes sense. This is the only thing right now that prevents me from using this module.
Thanks!

#1
hmm - interesting problem. It probably does occur because node_save() is used to store the updates to the node. I'd prefer not to dispense with this, since this allows for automatic tracking of revisions, etc.
#2
I found the solution to my problem. I know this is a very obscure issue, but on the off chance someone runs into this.. You just need to make sure the vocabulary or term's permissions are set to List for all users, in Taxonomy Access.. If the term is visibly listed on the node, it won't get reset, even if an unprivileged user (someone who can't use that term in their own content) submits on a volunteer timeslot node.
#3
ok - thanks for the update
#4
Automatically closed -- issue fixed for two weeks with no activity.