I get this error in my logs:

TypeError: Argument 4 passed to Drupal\\group_exclusive\\GroupUserRegisterForm::__construct() must be an instance of Drupal\\group\\Entity\\GroupInterface, null given, called in drupal-8.4.3/html/modules/contrib/mutual_credit/modules/group_exclusive/src/GroupUserRegisterForm.php on line 42 in drupal-8.4.3/html/modules/contrib/mutual_credit/modules/group_exclusive/src/GroupUserRegisterForm.php on line 24

Comments

SocialNicheGuru created an issue. See original summary.

matslats’s picture

matslats CreditAttribution: matslats commented

The form builder is assuming there is a group id in the path.
So I would need at least the path to debug, which I may not do.
I realised today that this module, which was coded because the group module was so far from ready, could probably be mostly performed by field settings, but I don't have time to look in detail. This is deprecated.

matslats’s picture

matslats CreditAttribution: matslats commented

the module tries to make you create users IN a group only because every user must be in 1 and only 1 group.
Therefore admin/people create shouldn't be accessible

SocialNicheGuru’s picture

SocialNicheGuru CreditAttribution: SocialNicheGuru commented

so users cannot be in multiple groups? they can only be in one group? ohhh that could be an issue with what we are trying to do.

matslats’s picture

matslats CreditAttribution: matslats commented

When I was doing this for CES there was one groupt-type called exchange which was mutually exclusive. In CES each member is in one and only one exchange, and has access to only the currency of that exchange.
If members are in multiple groups it opens up an avenue for fraud, and also complicates the UI because they have more options to pay more people in more currencies. For example I'm in group A and B and I want to pay someone in group B, the system has to work out that I probably want to use currency B. If want to pay someone in group C, however I need to via clearingcentral.
I'm happy to talk about your overall approach to this...

SocialNicheGuru’s picture

SocialNicheGuru CreditAttribution: SocialNicheGuru commented
Title: WSOD admin/people/create » WSOD admin/people/create - change behavior of group_exclusive

I get that.

I was thinking that not every group would be an exchange.

I am using the group module and have created other group types, closed and open.
Group_exclusive added an exclusive group type.

I would think that only the fields for community accounting would show up in the group_exclusive group type and groups created from them.

Instead the fields show up in all group types.

I think this is a bug in the module.

thus I should be able to create a user.
The user doesn't have to be assigned to the exclusive_group but can be.

There should be a setting asking if you want uses to be part of more than one exchange group type. If the answer is no, then they are just assigned to one exclusive group.

matslats’s picture

matslats CreditAttribution: matslats commented

group_exclusive forces every member to be in one and only one group of that type.
That means that in order to create a user you have to do it from within a (exclusive) group context.
It should not affect other group types.
There's not enough info here to debug.
I'm not supporting this module or mcapi_exchanges which depends on it.