Ok, based off your ACL structure it's working as intended. I'll give an example based off your ACL.
I am a member of CBMod. This means I can edit anyone that is in the below.
- Registered
- - Member
- - - Bestyrelse
Now CBMod is a parent of "Bestyrelse", but it is not a parent of "Festudvalg" and thus has no permission to edit them as you maybe expecting (again, ACL can be very confusing). Everything works in parent and child like relationships.
ACL isn't really what should be controlling access. Joomla does this through Assets and those assets are different roles like edit, delete, etc.. however CB doesn't use those, yet, and thus is purely based off the usergroup it self which in J1.7 there is no clearcut way of how it should behave as a parent and child relationship.
At this point I would say issue is solved as much as we can solve it with current implementation. We're saving ACL rewrite for CB 2.0 and really don't want to have to do a rewrite for a 1.x release as it could cause a lot of issues for backwards compatibility.
Kyle (Krileon)
Community Builder Team Member
Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums
CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.