-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public Access - Child Node Permissions #17709
Comments
Hi there @parxal! Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better. We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions. Thanks, from your friendly Umbraco GitHub bot 🤖 🙂 |
Hi @parxal , thank you for reporting this issue. |
@NguyenThuyLan Hi, do you know what's the priority to fix this issue? |
Hi @parxal, Thanks for reporting this 👍 I'll have a look at the root cause this week, then I'll have more info. |
Fixed in #17797 |
* Don't overwrite ancestor configurations for public access (#17709) * Fix spacings
Will be released in V15.1.1 soon 👍 |
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
14.3.1
Bug summary
I have a parent node with several child nodes. The parent node has public access settings defined. Whenever I create a child node under this parent, it inherits the permissions from the parent.
Use case: I change the permissions of a single child node, and Umbraco applies this change to all the siblings and the parent node as well. Shouldn't the change affect only that specific child node?
Specifics
No response
Steps to reproduce
1 - Create a Node (Parent)
2 - Assign public access roles (Parent)
3 - Create a child Node
4 - Change public access roles (Child node)
5 - Check Parent Node Permissions. Will notice that parent public access permissions were changed.
Expected result / actual result
When I change the public access settings of a specific node, it should only apply to that node itself and not to its siblings or parent.
This item has been added to our backlog AB#46945
The text was updated successfully, but these errors were encountered: