Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I am evaluating new functionality on the content overview page of drupal. Currently in a two roles setup a contributor can add/edit/delete own and and editor can add/edit/delete all of a specific content type. Often the case is that a contributor will upload content which will be unpublished up until it is published either by her or her editor.
Drupal correctly does not allow other contributors of accessing not published content but the same is true for editors as well. I could not figure out a possible permission combination to allow such behaviour.
Is that what the system intends to do or is this a bug?
Comments
Comment #1
dawehnerWell, we do have 'bypass node access', so you can already "achieve" that, so this is really more like a feature to be honest.
Comment #2
tassos CreditAttribution: tassos commentedBypassing node access should not be used in this situation as it might lead to undesired behaviour. For instance if there are other content types not in the contributor/editor relationship none of them should be able to access unpublished content.
The content overview page is a place that gives and overview of content of the system. It should respect individual user access level. If a user is not allowed to add/edit/view she should not be presented with the option. Moreover if a user is able to edit/delete all content from a *particular content type* then she should be able to do so.
Comment #3
tassos CreditAttribution: tassos commentedI re enable it as a bug report as the answer to 'bypass node access' has different scope than this particular problem.
Comment #4
jelo CreditAttribution: jelo commentedI am very interested in this as well. I might be imagining this, but wasn't there a permission called "View unpublished content" in Drupal already that allowed this? In my D7 site I can only find "View own unpublished content" which is a problem. Maybe I had seen this on a site where a module provided this extra permission.
Comment #13
LendudeCleaning up old bugs.
This is indeed not possible, but it is not possible by design, so changing that would be a feature request as @dawehner pointed out in #1. Setting back to 'Feature request'.
With the addition of Content moderation to core, there might be more options now to get this to work than there were when this was originally reported, so there might be workarounds available now.