I use TAC for the access to some node. But 2 users can have access to the edition of one node. I fone of them unpublished the node, the other is unable to republish or edit it even if he has the access with TAC. I think that this present module can do this … any idea ?

Comments

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented
Status: Active » Postponed (maintainer needs more info)

You mean, that two users will edit the same node at the same time?
If so, I think that a possible way is:
* Add a CCK field to your content, for example "Being Edited" that can be enabled or disabled.
* If 1st user edits the node, the action - set the field to enabled.
* If 1st user submitted the node, the action - set the field to disabled.
* If 2nd user tries to edit a node with "Being Edited"=Enabled - he's redirected to another page with an explanation message.

Cheers,
Amitai

amogiz’s picture

amogiz commented

Thanx for your answer. In fact, my problem is different : with Taxonomy Access access i let 2 users (user1 & user2) to edit a certain node. There can be only one author by a node. So if user1 or 2 unpublish the node only the author node willl be able to publish it again. So for exemple, user1 is the author ; one day he unpublisges the node. Another day User2 (that is authorised by TAC) wants tu republish the node or only edit it to modify the content : it is not possible. I think it happens oftem that 2 users have to edit a content. Scuse for my bad english …

MediaMunkey’s picture

MediaMunkey commented

Hi, I believe this comes down to a fundamental problem with drupal that I myself and i'm sure others are trying to overcome.
If the node is unpublished no access modules of any kind that I know of will allow anyone to view that node unless the user has the 'administer nodes' access assigned to them.
By the sounds of things these 2 users you talk about do not have that access right and therefore can not view an unpublished node. I believe it is still possible for them to edit the node if they know the direct link to the edit page of the particular node but this isn't very helpful when they can't see the node in the first place.

So as far as I know, Workflow-ng can't help you here. Then again I haven't actually used Workflow-ng yet.

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented

I think once the CCK states will be implemented, it will be easier for you to create a workflow, since Unpublishing can/ will be done through a CCK state rather then the node's Publish.

fago’s picture

fago
Primary language German
Location Vienna
commented

yep, that would help! Plus what would be needed would be an action to change node access - then one can define new states per CCK and configure access control for them with the help of the action and workflow-ng.

acrollet’s picture

acrollet commented

I've had luck with having workflow-ng set the content author to solve a problem where I wanted to let more than one person edit a node...