Problem/Motivation

I often have the situation that i want group functionality for (1)an existing entity type, and (2) existing relations.
The first is in #3169381: Allow any entity type as group.
The second is this one.

Example: I want a commerce store to act as a group, and orders and products be group content.
Instead of duplicating the relations, it would be far better if - besides the default "GroupContent" plugin, i can add a plugin that uses the existing references as group content relation.

Proposed resolution

Pluginify GroupContent.

Remaining tasks

Explore, discuss, code

User interface changes

API changes

Data model changes

Comments

geek-merlin created an issue. See original summary.

kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
commented
Status: Active » Postponed

I don't see this happening anytime soon as Group2/3 heavily rely on knowing how the relationships are represented in the database. The code is there, as we could, for instance, adjust the output of GroupRelationshipQueryAlter::getMembershipJoinLeftField() et al.

But I'm hesitant to implement this feature when a new major version is about to be released. Maybe for v4 I'd consider this, but right now it's not in the cards. Too much risk vs the reward side of things.