Group Membership State - None - Causes Crashes

Created on 26 November 2018, almost 6 years ago
Updated 13 October 2023, about 1 year ago

Having members of a group with membership state set to "- None -" breaks certain functionality. I've included a screenshot of one such case when hitting the endpoint /group/%group/content (the Related entities tab "view" included with the group module).

I'm still trying to discern the reasoning and use cases for having such a membership state, but so far it seems to me that it implies the same thing as having no membership in a group, AND leads to undefined behavior, probably elsewhere on the site than the case mentioned above.

Technically, I'm noticing that a user of a group with a membership state of "- None -" has a record in the group_content_field_data table (of the group content type "membership" type) AND has no correlating (by entity_id foreign key relation) record in the group_content__group_membership_state table.

So, is this really the intended functionality?

At this point I believe it may be worth considering the purpose of this membership state and whether removing it (the "- None -" state) will make for a clearer user experience and eliminate undefined behavior that programmers will have to accommodate in development.

Steps to Reproduce:

πŸ› Bug report
Status

Closed: outdated

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States percoction

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024