Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.The permissions provided by group node are confusing right now. We should look into clarifying those so that people know which permissions relate to the relationship (GroupContent) and which relate to the subject (Node).
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | Screen Shot 2017-11-20 at 17.43.45.png | 192.4 KB | kristiaanvandeneynde |
| #6 | group-2702735-6.patch | 20.47 KB | kristiaanvandeneynde |
| |||
Comments
Comment #2
rosemeria CreditAttribution: rosemeria as a volunteer commentedHello Kristiaan, thank you for creating this awesome module for D8.
Let's start the conversation on this issue.
Currently for permission roles you have...
Anonymous: This is the same as the global Anonymous role, meaning the user has no account.
Outsider: This means the user has an account on the site, but is not a member of the group.
Member: The default role for anyone in the group. Behaves like the "Authenticated user" role does globally.
Maybe something like this and add a needed group manger role? Drupal creates online communities (instead of saying websites) and the Group module helps the online community to organize and communicate both privately and publicly.
Public - User is anonymous, user is not logged-in.
Community Member - User is has an account on the site, but is not a member of the group.
Group Member - User is member of the group.
Group Manager - User is manager of the group.
-Rose
Comment #3
kristiaanvandeneyndeHi there!
You can specify any roles you want outside of the three "automatic" roles Anonymous, Outsider and Member. So there's no need for us to ship with a manager role.
As for the labeling of the default roles, I think we have another issue for that somewhere in the queue. It's an artifact from how things were named in Group 7 and it may be hard to change this up so late in the alpha cycle. We are about to go beta and then ideally we won't change any core elements such as these.
This issue is actually about the permissions the Group Node module exposes to the group permission form. They are a bit vaguely named and should have much user friendlier labels.
Comment #4
rosemeria CreditAttribution: rosemeria as a volunteer commentedHello Kristiaan,
OK, taking a stab to this... release candidate blocker
Group Node:
Access group node overview
Access to all group nodes, regardless of node type
%node_type: Create new content
User can create %node_type(s) in this group
%node_type: Delete any content
User can delete any %node_type in this group
%node_type: Delete own content
User can delete their own %node_type(s) in this group
%node_type: Edit any content
User can edit any %node_type in this group
%node_type: Edit own content
User can edit their own %node_type(s) in this group
%node_type: View content
User can view %node_type(s) in this group
%node_type: View unpublished content
User can View unpublished %node_type(s) in this group
**Example: What it looks likes for node type Article**
Access group node overview
Access to all group nodes, regardless of node type
Article: Create new content
User can create Article(s) in this group
Article: Delete any content
User can delete any Article in this group
Article: Delete own content
User can delete their own Article(s) in this group
Article: Edit any content
User can edit any Article in this group
Article: Edit own content
User can edit their own Article(s) in this group
Article: View content
User can view Article(s) in this group
Article: View unpublished content
User can View unpublished Article(s) in this group
Comment #5
kristiaanvandeneyndeThanks, I'll take this into account when I start working on a patch.
Comment #6
kristiaanvandeneyndeHere's a first stab at this. It could still use improvement but is already far more clear than the old UI.
Comment #8
kristiaanvandeneynde