Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access collection drop down list of Group Entitities no longer showing other Groups (Trac #3708) #3708

Closed
elgg-gitbot opened this issue Feb 16, 2013 · 2 comments

Comments

@elgg-gitbot
Copy link

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...

@elgg-gitbot
Copy link
Author

cash wrote on 41625264-01-14

The change was intentional. Reasons:

  • 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.

@elgg-gitbot
Copy link
Author

trac user tomv wrote on 41625821-11-20

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant