I have 2 nodes of the same content type created and they are identical except that one is created by user 1 and the other with the role of webmaster

Devel displays that both of them can by updated by the webmaster and that is also how I configure tac lite

http://screencast.com/t/m1hSjG6hw7E
(same information for both nodes)

However, I can only access 1 node not both. I am stumped since I though that the devel information was reliable.

Also the gid column that tac lite uses in the node_access table is the role id? I see that gid/roleid 5 is stored but the webmaster role has id 4. Seemed a bit strange to me.

I am working on a deadline so if you would give any help its greatly appreciated. If you want I can give you access to my site in case I will pay 50 EURO per hour (I am on a deadline so a bit desperate)

You can contact me at my profile or through skype at "tom.pester"

Regards, Tom

Comments

Dave Cohen’s picture

Dave Cohen commented
Status: Active » Postponed (maintainer needs more info)

The gid is a term id, not a role id.

Could be as simple as using a different input format on the two nodes. That's one of Drupal's trickiest "features".

Whatever it is, its probably due to some other module granting the user access and not tac_lite.

show the same screenshot for the other node. Are they tagged with the same term and which input filters do they use?

jameswoods’s picture

jameswoods commented

I had the same sort of issue, seemingly identical nodes, but some roles couldn't access one of the nodes, despite having the proper permissions in tac_lite. Turns out that Dave "the man" Cohen was correct. It was different input format permissions that was screwing me up. As soon as I made sure that my roles had permissions to the proper input formats, all was well in my little world.

Thanks Dave 8^)

-James

Dave Cohen’s picture

Dave Cohen commented
Status: Postponed (maintainer needs more info) » Fixed

Cool. And since this issue is a year old, resolving.

Status: Fixed » Closed (fixed)

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