I don't understand the point of this feature. When I enable this setting, I want to be able to say for this node, only these roles have view access.

However, the form on this page looks like a copy of the main form found on the content type, which makes no sense. It repeats all actions (view any, view own, edit any, edit own) when it seems like it should only have settings specific to the node being edited.

Comments

kevinquillen created an issue. See original summary.

kevinquillen’s picture

kevinquillen commented
Issue summary: View changes
gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Version: 8.x-1.x-dev » 2.0.x-dev

This should go into the version compatible with Drupal 10.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Parent issue: » #3142990: [meta] Fix Content Access UX issues.

Added meta issue as parent.

kevinquillen’s picture

kevinquillen commented

Thank you!

steven jones’s picture

steven jones commented
Status: Active » Closed (works as designed)

I guess it's weird...but the settings do make sense, don't they?

In that the settings really do apply specifically to the individual node, overriding the defaults set for the node type.

Within that, it does make sense for the view / view own type settings, since the owner of node could change in its lifetime, and you might want different permissions during that.

I'm going to mark this as won't fix, because although it is confusing, I believe that it's correct at the moment.

We're working on moving to a better UI for managing these permissions in #3569619: Move configuration to Drupal core permissions user interface and maybe we'll add that for individual nodes, and then maybe the UI will be clearer!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.