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 don't understand the purpose of the per content type "ROLE BASED ACCESS CONTROL SETTINGS" of "edit any...", "edit own...", "delete any...", "delete own..."?
Isn't this the same as the Node module permissions like "[content_type]: Edit any content", "[content_type]: Edit own content", etc?
Comments
Comment #1
bigdave CreditAttribution: bigdave commentedHello,
I was wondering if anyone had a chance to review this question of mine.
Thanks,
David Steven
Comment #2
bigdave CreditAttribution: bigdave commentedHate to be that guy, but....
Comment #3
salvisIt's a good question and there seems to be no good answer...
Internally, it's a different mechanism, but the result is probably the same.
Comment #4
bigdave CreditAttribution: bigdave commentedWould it be correct to say that it exists so you can give the permission to someone to configure these settings for content types without having to give them access to the node module permissions?
Comment #5
fabioknoedt CreditAttribution: fabioknoedt commentedThese permissions are different:
"edit any..." in Drupal core context allows a role to edit any node of a content type
"edit any..." in OG context allows a role (inside a group) to edit any node of a content type from that specific group, not from ANY group of the website
Clear?
Comment #6
salvis@fabioknoedt: We're not in OG, we're in CA. There are no "groups" here.
Comment #7
fabioknoedt CreditAttribution: fabioknoedt commentedUfff... my bad! I was googling and I didn't see the Project. Sorry guys!
Comment #8
gisleYes. And they are the same. Content Access just display them to give you a one page overview of all major permissions. README.md has been updated to make this clear.
If you got an email about this Issue status update, it is because you at one time (possibly a very long time ago), subscribed to it. To learn how to unsubscribe yourself, please visit: https://www.drupal.org/project/webmasters/issues/3142987