I see there is a guser module which would meet my needs but which has no d8 releases yet.
Should I make a guser module as part of the group module in d8?
I will happy make a simple contentEnabler plugin which can be extended later.
Should the group module not be providing a contentEnabler for every core ContentEntityType?

Comments

matslats created an issue.

ctrlADel’s picture

Hi there, creator of guser here. Porting guser over to D8 is on my todo list but I haven't had much time to familiarize myself with D8 group or get started on the actual porting. If you have the time/need I would be happy to provide some help to get a port started.

In general it would make sense for group to provide plugins for all of core's content entities except probably user. In D7 I believe kristiaan specifically didn't make users group content because of the possible confusion between users as group content and users as group members. That confusion is probably just as likely in D8 so leaving guser as it's own module I think makes sense.

kristiaanvandeneynde’s picture

I would love to see a D8 release of guser as a standalone module. In D8, it should be really easy to accomplish with the new plugin we provide. Have a look at the group_membership plugin to get started, you'll probably want to clear out all the methods that override the base class, though :)

ctrlADel’s picture

In D8, it should be really easy to accomplish with the new plugin we provide.

The plugin was indeed easy. Now for all the useful user interfaces and those pesky access controls.

maxplus’s picture

Yes,
guser for D8 would be great.
I'm using guser for D7 right now and I like it a lot, It is really a very useful add on for the group module!