In a Group, But Not Really?
Permalink
I'm having trouble understanding some group behavior...
A user placed inside a subgroup is apparently not considered to be in the parent group. Shouldn't a user in a subgroup also be in the parent group by virtue of the hierarchy? In other words, if "Division A" is a child of "Organization 1", then shouldn't a user in "Division A" be shown when listing users of "Organization 1"?
As it is now, they are not, and it makes no sense to me. Is that the intended behavior? Can anyone confirm and/or shed some light?
To replicate, just create a group hierarchy and add a user to a child group. Then, go to the "Search Users" dashboard page and search for users in the parent group. Members of the child group do not appear.
Thanks for any help or insight,
-Steve
A user placed inside a subgroup is apparently not considered to be in the parent group. Shouldn't a user in a subgroup also be in the parent group by virtue of the hierarchy? In other words, if "Division A" is a child of "Organization 1", then shouldn't a user in "Division A" be shown when listing users of "Organization 1"?
As it is now, they are not, and it makes no sense to me. Is that the intended behavior? Can anyone confirm and/or shed some light?
To replicate, just create a group hierarchy and add a user to a child group. Then, go to the "Search Users" dashboard page and search for users in the parent group. Members of the child group do not appear.
Thanks for any help or insight,
-Steve
That sounds like a bug. It's the intended behavior that users in sub-groups show up when you search through the parent groups, run an inGroup() method on the user/parent group, etc...
Ah, great, good to know. A project I'm developing relies on that behavior. Thanks for clarifying.
-Steve
-Steve
Hi Andrew,
Has this bug been addressed? i'm suspecting that this something im running into at the moment.
Has this bug been addressed? i'm suspecting that this something im running into at the moment.
I've just run into this problem as well. Is there either an ETA on when this will be addressed or perhaps a workaround?
Also, I don't see a bug report for this. Should one be opened?
This will be fixed in concrete5 8.2.0.
