I have a role (let's say EDITOR) which has access to term "test" of vocabulary A.
I have 3 nodes with vocabulary A. On thoses 3 nodes, EDITOR has acces to the "edit" tab (everything's ok right now).
An administrator "unpublish" one of the node. EDITOR now has access to two nodes (still all right)
An administrator "publish" the node previously unpublished. EDITOR can now access the node BUT the "edit" tab is not shown.

I use Drupal 6.3 and MySQL.

Thanks

Comments

greg911’s picture

greg911 commented

I it may help....
I found out that adding permissions alter the node_access table. When you unpublish the node, all permissions returns to the "default" permission for this role. Or when you "publish it back" the node_access is not updated. I imagine that this problem may also occur when you create new node (not verified )

cpugeniusmv’s picture

cpugeniusmv commented

I tried this out on one of the sites I'm working on (D6.3/MySQL) and can't reproduce it. All of the relevant entries in node_access remain the same when i unpublish and republish a taxonomy_access-controlled node.

greg911’s picture

greg911 commented
Category: task » support

I currently have two groups (on top of the "default one") : One "Admin" which is Allowed everything by default and one "Editor" which has Allow Update only on one taxonomy term and ignore for the rest.
How's your setup ?
Is there any module known to "interfere" with the node_access table ?

Thanks !!!

cpugeniusmv’s picture

cpugeniusmv commented

The role I tried it on had these defaults: ignore read, ignore edit, ignore delete, but allow create. And then for one of the terms he could edit and delete.

What other modules do you have enabled?

greg911’s picture

greg911 commented

It seems to be one of our in-house module that "broke" the node api and alters it.... Still investigating
I'll keep you posted!
Thanks for your quick response

greg911’s picture

greg911 commented
Status: Active » Fixed

Finally, I got it !
A bad hook_form_alter and hook_nodeapi in our custom developped modules where the problems in my "misbehaving Taxonomy Access Module" Thanks cpugeniusmv for your support and thanks to the Taxonomy Access module team for delivering such a lifesaver module.

This module should be included in core (IMO) beacause it allows easy separation of administration tasks over the content.

greg911’s picture

greg911 commented
Status: Fixed » Closed (fixed)