Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I (finally) got ACL to work properly, based on group permissions. However when I create a new user (Users/add) it automagically.. I mean.. autoinconveniently creates a User ARO..
While this is not really a big problem, I would like my ARO table to stay as clean as possible. Just my groups.
How do I disable the automatic creation of a User ARO object when creating a new user through CRUD?
i had the same problem and, like you, i said to myself “its not a big deal as long as it’s working”… but when i started to have more and more users and when i added new groups, i found that ACL was not working correctly.. If you’re using a group-based permissions, you MUST ONLY have groups in your AROS table.
Brief, the documentation says that you need to add the
bindNode()in your Users model if you want a group-based ACL, but what they don’t tell you is that for group-based permissions your User model doesn’t have to implement the requester behavior and you don’t need the parentNode() neither. Remove those two and it should be ok.I added a note on the documentation, i hope it gets published 🙂
Good Luck