I am using D7.50 with latest Views installed.

I created a new view with Groups. Format is unformatted list, show is Fields.
I added a field of Group: Rendered Group to display in path /teams.
The field settings are: Display: Complete entity, View mode: Group, Bypass access (checked).

Reason I did this is because, I wish to display all available groups of this group type on /teams which a user can request membership. If I do not check "bypass access" then only the groups show if I have membership. This way, all groups show properly. Those I am not member of display "Request Membership" and those I am part of shows no button.

The issue: the "request membership" buttons do not correspond to the proper group it is with. Example:

Group 1 : Request Membership
Group 2 : Request Membership
Group 3 : Request Membership
Group 4 : Request Membership

If I choose to "Request Membership" for Group 3, It is show in the system that I requested membership for "Group 1". If I refresh page of /teams, Group 1 does not display button.

If I am already a member of Group 1 and again I try to choose the "Request Membership" of any group below it, the system logs my request as for Group 2. ... and so forth.
The request button in this case, always corresponds to the next group in array that I am not the member of instead of the group which I choose.

Perhaps it is a bug? or perhaps I am using Views incorrectly this way? Please advise. Thanks!

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Tankeroo created an issue. See original summary.

Tankeroo’s picture

Wanted to add some screen shots for better explanation. Maybe I did something wrong in views or maybe it's a bug.

davidburns’s picture

Confirmed this is an issue. I have a view of rendered group entities with membership form displayed on each group.

Both forms have the same submit action and the submit handler can't tell the difference between multiple buttons on one page, so it's just grabbing the first available.

Soul88’s picture

Status: Active » Closed (outdated)

We thank everyone for their collaboration on this issue, but as the D7 version is no longer supported, we will now close all D7 issues to keep the issue queue a bit tidier. This information won't go anywhere, it just won't show up on the list of open issues anymore.

Please see: https://www.drupal.org/project/group/issues/3163655 and https://www.drupal.org/project/group/issues/3203863#comment-14100281 for more details.