Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I have looked into this again, but there does not seem to be a way to allow editors to edit a node that has not yet been published. We use the module to allow several people to collaboratively work on a node for publication and, once that is done, to do occasional updates afterwards. Without the first step working, we cannot go to the second one. Is there any way to change the settings so that unpublished nodes can be edited by editors and not only node-authors? Thanks for any support!
I have looked into this some more. Using the Publish Content module it is possible to allow editors to see an unpublished node, but even with Publish Content it is not possible to allow them to edit a node (unless you allow them to edit all nodes, of course, but that makes the use of Coherent Access rather pointless).
There is a lot of interest in this and I think it would be marvellous if Coherent Access could make that work. Without this feature, we cannot use the module as we will never get the content to the "published" stage in the first instance.
I believe the functionality you are looking for would be provided by setting the node to private, and assigning edit/view permissions as appropriate. I had configuration problems when initially setting this up (more details here: #605852: Setting node to "Private" does not limit view access.).
Please repost after considering this advice if you are still having an issue.
Thanks for your posting and apologies for the delay in getting back - I did not receive an email from Drupal telling me that you had replied. Unfortunately, I cannot really test your suggestion. The problem is that while it does work at first, the second an editor makes a change to the node and saves it it "forgets" that it has been set to "private" and it also loses all memory of who the editors are.
This might relate to bug #605852; sadly, we do need node permissions (edit own content) and we had this set up many months before we installed coherent access. So if it were caused by this bug I would not know how to address the issue. Obviously, it could be something else too. Do you think this is related or should I open a new bug report?
Comments
Comment #1
Anonymous (not verified) commentedI have looked into this again, but there does not seem to be a way to allow editors to edit a node that has not yet been published. We use the module to allow several people to collaboratively work on a node for publication and, once that is done, to do occasional updates afterwards. Without the first step working, we cannot go to the second one. Is there any way to change the settings so that unpublished nodes can be edited by editors and not only node-authors? Thanks for any support!
Comment #2
Anonymous (not verified) commentedI have looked into this some more. Using the Publish Content module it is possible to allow editors to see an unpublished node, but even with Publish Content it is not possible to allow them to edit a node (unless you allow them to edit all nodes, of course, but that makes the use of Coherent Access rather pointless).
There is a lot of interest in this and I think it would be marvellous if Coherent Access could make that work. Without this feature, we cannot use the module as we will never get the content to the "published" stage in the first instance.
Comment #3
evoltech commentedI believe the functionality you are looking for would be provided by setting the node to private, and assigning edit/view permissions as appropriate. I had configuration problems when initially setting this up (more details here: #605852: Setting node to "Private" does not limit view access.).
Please repost after considering this advice if you are still having an issue.
Comment #4
evoltech commentedComment #5
Anonymous (not verified) commentedThanks for your posting and apologies for the delay in getting back - I did not receive an email from Drupal telling me that you had replied. Unfortunately, I cannot really test your suggestion. The problem is that while it does work at first, the second an editor makes a change to the node and saves it it "forgets" that it has been set to "private" and it also loses all memory of who the editors are.
This might relate to bug #605852; sadly, we do need node permissions (edit own content) and we had this set up many months before we installed coherent access. So if it were caused by this bug I would not know how to address the issue. Obviously, it could be something else too. Do you think this is related or should I open a new bug report?
Comment #6
Anonymous (not verified) commentedAddendum: I have looked a little more into the bug I described in #5, see #830358: Viewers, editors and "private" information lost after node upgrade with new nodes
Comment #7
dpatte commentedsub
Yes, it would be nice if all co-editors had the same rights (if the author can see a node, the coeditors can as well)