#3708 closed Defect (wontfix)
Access collection drop down list of Group Entitities no longer showing other Groups
| Reported by: | tomv | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Needs Review |
| Component: | Core | Version: | 1.8 Beta |
| Severity: | minor | Keywords: | |
| Cc: | brett@… | Difficulty: |
Description
In Elgg 1.7 when we add an entity like a new page or blog to a group like a group 'Dev Team' we could select for read access also other group, like 'Group:All Personnel'.
In Elgg 1.8 it seems we can only assign read access to the same group or to public, private, friends, a friend collection. This makes it impossible to have a core group of people that can change items, like in our case 'Group:Dev Team' and a wider group of people that can follow but not change like in our case the people in one company...
Change History (2)
comment:1 Changed 22 months ago by cash
- Resolution set to wontfix
- Status changed from new to closed
comment:2 Changed 22 months ago by tomv
Ok, thanks. Sounds ok to me. Access rights indeed are confusing to many users, so simplifying is welcome. We could make a new access drop down view, which which shows an extended version for those cases where it could be useful.

The change was intentional. Reasons:
You should be able to modify this behavior with a plugin. If this is difficult, please open a ticket about making this easier. It's possible the access list should be generated with a plugin hook (don't remember if it is or not).
Also, you may want to take a look at the shared access collection plugin for 1.8. I haven't used it but it is supposed to support creating an access list that is shared among users.