Problem/Motivation
When one adds a group member and there is a node with ID equal to userID, the node also becomes the group member.
Steps to reproduce
1. Install group module ( https://www.drupal.org/project/group ) version 3.0․
2. Enable group and group node modules.
3. Create Group Type -> Group1 (admin/group/types/add) and install /admin/group/types/manage/group1/content basic_page(content type).
4. Create 2 nodes. title = Node1 (url = lndo.site/node/1) and title = Node2 (url = lndo.site/node/2).
5. Create 2 new users, ids will be 2 and 3.
6. Create a group Test.
7. Go to group Nodes ( group/1/nodes ).
Expected result: Empty list
Actual result: A node with id 1 appears in a list.
And if one adds new member whose id exists in nodes ids (ex. user/2 , node/2) the node will appear in a list (becomes group member content)
| Comment | File | Size | Author |
|---|---|---|---|
| #29 | group-3315779-29-2.patch | 3.66 KB | kristiaanvandeneynde |
| #29 | group-3315779-29-3.patch | 3.66 KB | kristiaanvandeneynde |
| Screenshot from 2022-10-17 18-39-59.png | 90.91 KB | artyom hovasapyan | |
| Screenshot from 2022-10-17 18-56-37.png | 81.07 KB | artyom hovasapyan | |
| Screenshot from 2022-10-17 18-56-37.png | 81.07 KB | artyom hovasapyan |
Issue fork group-3315779
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
artyom hovasapyan commentedComment #3
artyom hovasapyan commentedComment #4
artyom hovasapyan commentedComment #5
artyom hovasapyan commentedComment #6
artyom hovasapyan commentedComment #7
artyom hovasapyan commentedComment #8
artyom hovasapyan commentedComment #9
artyom hovasapyan commentedComment #10
artyom hovasapyan commentedComment #12
artyom hovasapyan commentedComment #13
artyom hovasapyan commentedComment #15
artyom hovasapyan commentedComment #16
artyom hovasapyan commentedComment #17
artyom hovasapyan commentedComment #18
artyom hovasapyan commentedComment #19
artyom hovasapyan commentedComment #20
ultimikeI can confirm this behavior in Group 3.0.0-beta3 and that applying the patch in #19 appears to solve this issue.
-mike
Comment #21
kksandr commentedComment #22
kksandr commentedComment #23
dudeweb commentedI confirm I had that weird thing as well. Adds to the other bug here https://www.drupal.org/project/group/issues/2842630
Comment #24
dudeweb commentedPtach works. Thanks!
Comment #26
kristiaanvandeneyndeThanks for the report, will look into this. Meanwhile crediting FiNeX for their detailed report in #3315579: "Group nodes (content)" view displays wrong data.
Comment #27
ultimikeComment #28
finn lewisMe too!
I confirm this behaviour in Group 3.0.0-beta3 and that applying the patch in #19 appears to solve this issue.
Comment #29
kristiaanvandeneyndeTry one of these.
Comment #30
finn lewisThanks for the updated patches @kristiaanvandeneynde.
Tested group-3315779-29-3.patch from #29 and it works for me. Our duplicate content listings have gone. Thank you!
Guessing you might want someone to test the 2.x version before making this RTBC?
Comment #31
kristiaanvandeneyndeSeems to fix things, would be awesome if someone could write a test for this. (I manually tested the v2 patch and don't have time to write automated tests for the OOTB views configs)
Comment #33
ultimikeThank you, @kristiaanvandeneynde!
-mike