Active
Project:
Group
Version:
8.x-1.x-dev
Component:
Group Node (gnode)
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Jul 2016 at 07:54 UTC
Updated:
5 Nov 2019 at 22:43 UTC
Jump to comment: Most recent
Comments
Comment #2
kristiaanvandeneyndeI am more in favor of your second idea. Although the use case of relating a node to a group should be far less common than the case where a node is created in a group (using the wizard).
In some way it makes sense that someone with enough power to group global nodes (usually admins), that the node is then stripped from anyone who isn't part of the group.
Imagine the use case where there is a group called "Review reported content". When content is reported, it is added to that group so only reviewers can still see it. Once reviewed, it could be made public again or have further action taken against it.
Comment #3
kristiaanvandeneyndeComment #4
dalra commentedHaving a permission to Add own existing content would prevent users from breaking the site.
Any chance for this to be implemented soon?
Comment #5
zenimagine commentedComment #6
dalra commentedIt would be great to see this implemented in the next release.
There are many use cases where only the node author should be able to add it to a group.
Comment #7
dwwAuthors aren't necessarily men. Updated title and summary accordingly.
Meanwhile, +1 to using permissions for this, not hard-coding the specific behavior.
Thanks,
-Derek
Comment #8
dianacastillo commentedhas anyone done any work on this I can add to or test?
Comment #9
dianacastillo commentedI know this is not the "right " way to do it but as a quick hack I added in
/modules/contrib/group/modules/gcontent_field/src/Plugin/Field/FieldWidget/GroupSelectorWidget.php
in the function getAllowedgroups
$account = $this->currentUser ->get Account;
foreach ($groups as group){
if ($group->getMember($account}{
}else{
continue;
}