I am using TAC Lite to try and allow individual users access to edit pages with certain terms.

Example:
- Taxonomy Vocabulary of Departments
- Terms in the Vocabulary are the different organizational departments
- Selected the Vocab "Departments" in the settings
- Scheme 1 allows anonymous and authenticated users to view all terms in Vocab "Departments"
- Scheme 2 is for Edit rights on Department terms and it is set to None on all roles
- Using the "per user access" to allow editing on certain terms so that the assigned person per department can edit nodes tagged with the associated department term.

This works fine the assigned user on the first initial attempt at editing. After permission is given to the user for the term and permissions are rebuilt, the user can log in and see the edit tab on nodes that are tagged with the given term.

Problem area:
After the user edits and saves the node, the editing tab is no longer available on that node for that user. If I rebuild permissions, the edit tab returns for the user.

I have tried this and get the same result with version 6.x-1.5 and the latest dev version as of 2011-08-04.

I suspect that I am doing something wrong with my setup. Thank you for any assistance.

Dan

CommentFileSizeAuthor
#1 screenshot - error TAC Lite.png47.15 KBdaniel-san

Comments

daniel-san’s picture

daniel-san commented
StatusFileSize
new screenshot - error TAC Lite.png47.15 KB

I have been investigating this by using the Devel Node Access module. Using the debugging tool, the following shows up after the user updates the node.

The errors are in a table and may not show up here properly, so I am attaching a screenshot as well.

node	prio	status	realm	gid	view	update	delete	explained
1103	?	alien	all	0	1′	0	0	All users may view this node.
1103	– 	missing	tac_lite	34	1			
1103	– 	missing	tac_lite_scheme_2	34		1		

You have errors in your {node_access} table! You may be able to fix these for now by running Rebuild permissions, but this is likely to destroy the evidence and make it impossible to identify the underlying issues. If you don't fix those, the errors will probably come back again. 
DON'T do this just yet if you intend to ask for help with this situation.
daniel-san’s picture

daniel-san commented

UPDATE: Created a new Vocabulary and some terms. Set up TAC Lite to use new vocabulary and terms and gave User access rights to edit nodes with new terms and it worked perfectly.

The error that I've been dealing with above seems to be related to Vocabulary and Terms that were created prior to the install of TAC Lite.

Dave Cohen’s picture

Dave Cohen commented
Status: Active » Fixed

It should work with terms created before tac_lite was installed. Maybe the old vocab used free tagging? Maybe you never set up a tac_lite scheme with the old vocab?

Is this fixed?

daniel-san’s picture

daniel-san commented

Hey Dave,

Thanks for the reminder regarding the free tagging. I went back and sure enough, it was set to allow tags. So sorry for wasting any of your time. This will be marked as fixed.

You would think that after this many years of using Drupal and helping others learn the ins and outs of learning the system, I would have paid better attention to the instructions. I DID read them, but I just didn't go back and check for free tagging.

Thanks again and thank you even more for working on this module. I think it is the only user access solution that could have solved my particular use case.

Take care,
Dan

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.