A bug was reported where user profile settings do not reflect group membership after bulk inviting users to a group. kmvoges shared an error message and log details, and sam requested that it be added to the fix list. techAPJ initially could not reproduce the issue, but later kmvoges provided repro steps and screenshots using a CSV invite method. The issue was further clarified by sam, who mentioned that no error message is displayed when trying to add a user who already exists in the group. The bug was eventually fixed by techAPJ via a GitHub pull request and commit.
When manualy trying to add them to that custom group (because you think something went wrong, an error occurs and a fatal error is seen in the logs.
So seemingly users are being added to the group, they also have access, only the profile settings do not correctly reflect the fact that they have been succesfully added to the group.
also reported via @bobmcneel we should get it fixed
@techAPJ can you add to your list
I just tested this on my dev env and I am unable to repro this.
I invited a user via bulk invite feature and specified group beta to be added by default. When the user redeemed that invite, I can see that he has been added to beta group.
User profile page:
Admin user page:
Admin group page:
Can you provide a screenshot for this? Along with repro steps.
the error is, try adding a user that already exists in the group, no message is displayed saying it is already in the group.
Use CSV to invite user to specific group and topic:
xxx@xxx.com,Beta,14
“14” is the specific topic that I am inviting them to.
The results are that you can see that they are added in the admin group page, but not in de admin user page and neither in their profile:
@sam just fixed this.
https://github.com/discourse/discourse/commit/4919ec4c44ab7f840aad891f1896fb7353fe8205
