You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
The text was updated successfully, but these errors were encountered:
people who were members of a lot of groups had huge drop down menus
people were accidentally setting the access to the wrong group and then surprised why no one else can see the file
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.
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.
Original ticket http://trac.elgg.org/ticket/3708 on 41569763-01-07 by trac user tomv, assigned to unknown.
Elgg version: 1.8 Beta
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...
The text was updated successfully, but these errors were encountered: