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

bigdave’s picture

bigdave commented

Hello,

I was wondering if anyone had a chance to review this question of mine.

Thanks,
David Steven

bigdave’s picture

bigdave commented

Hate to be that guy, but....

salvis’s picture

salvis
he/his
commented

It'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.

bigdave’s picture

bigdave commented

Would 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?

fabioknoedt’s picture

fabioknoedt commented

These 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?

salvis’s picture

salvis
he/his
commented

@fabioknoedt: We're not in OG, we're in CA. There are no "groups" here.

fabioknoedt’s picture

fabioknoedt commented

Ufff... my bad! I was googling and I didn't see the Project. Sorry guys!

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Version: 7.x-1.2-beta1 » 7.x-1.x-dev
Assigned: Unassigned » gisle
Issue summary: View changes
Status: Active » Fixed

Isn't this the same as the Node module permissions like "[content_type]: Edit any content", "[content_type]: Edit own content", etc?

Yes. 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

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.