- π¨π¦Canada minoroffense Ottawa, Canada
This appears to affect any View of content belonging to mulitple groups. Even the Path Alias list shows duplicate items now.
- π¨π¦Canada minoroffense Ottawa, Canada
This is a pretty problematic issue so I'm marking it as major.
- πΊπΈUnited States pcate
This appears to affect any View of content belonging to mulitple groups. Even the Path Alias list shows duplicate items now.
I can confirm I'm see this as well with Group 2.x when a content node is added to multiple groups. I'm seeing the duplicates on both the group node list and the regular
/admin/content
view. - πΉπThailand AlfTheCat
In my case this happens even when a node is just part of a single group.
Every single contextual view also repeats. Using 3.x
- πΉπThailand AlfTheCat
In my case the aggregation workaround didn't work for views using contextual filters (displays with fields of the node being viewed). Enabling aggregation or limiting the results to 1 item resulted in a fatal error.
The dirty work-around solution there is to instead set the number of items to display to 1 but skip the first result (offset 1).
i have the issue also, Drupal 9.5.9, Groups 3.1.0. Setting the view to use distinct is a workaround...
- πΉπThailand AlfTheCat
I'm also suspecting that a duplicate relationship is being created.
I feel like there might be some crucial information missing from the documentation. I was looking for the same thing that groups did in Drupal 7, to have a group reference field on a node and allow content to be added to a group that way, instead of only from the group page which is how it seems to be in 3.x.
I eventually replicated it by using entity reference for group selection and creation, and then use an ECA model to add the node to the group. I have a nagging intuition that however it is that the group module manages relationships between groups and users and nodes, that processes is firing multiple twice.
- ππΊHungary mxr576 Hungary
Applied the issue template so steps to reproduce can be added easily.
- π·πΈSerbia korinna
Turning the creator wizard off (as suggested by Kristiaan Van den Eynde in the Drupal slack channel) seems to be a workaround for the newly created groups. A new node added to the new group shows up only once on the /group/3/nodes view (and on the /admin/nodes view as well) and there is only one admin member on the /group/3/members view with Group creator role.
The existing ones still have the admin account displayed four times on the members view (twice without role and twice with Group creator role). The root cause of this is the same - the groups were previously created with the Group creator must complete their membership option selected.
By deleting one of the admin users (e.g. the one added with id: 2 to the group during its creation), there remains only one admin user in the group with Group creator role. It seems that this might still need a fix considering the existing data.
- Status changed to Closed: duplicate
over 1 year ago 1:47pm 11 September 2023 - π§πͺBelgium kristiaanvandeneynde Antwerp, Belgium
Issue will be fixed in π "Group creator must complete their membership" Wizard duplicates membership Needs review