-
Notifications
You must be signed in to change notification settings - Fork 10.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Admin UI web page crashed when deactivating user who is owner of at least one private group #25155
Comments
@debdutdeb @dudanogueira hey, guys! |
Is the api working? Have you checked that? |
Can't reproduce on the latest develop :/ |
(self-assignment was a mistake) |
Strange I get this when try to use API on FQDN:
And when I try curl to instance directly I get this error: |
Ok - can reproduce - the group needs to be private it seems. |
Updated in reproduce steps. |
I'm still on 4.3.3 and when I deactivate similar user I see modal about that private group and that user is owner of that group. And there is a red button - |
@ankar84 - it is true for all groups, not just private. Sorry about that, in the first case I didn't set it as a owner but leader 🙈 |
Another thing, just to make sure everyone following/coming to this thread knows, you can still deactivate a user using the API. Just the client is broken. |
Description:
Admin UI web page crashed when deactivating user who is owner of at least one chat.
If you deactivations user that not an owner of any chat - it's OK.
Steps to reproduce:
Expected behavior:
Admin UI not crashed on deactivating any users
Actual behavior:
Server Setup Information:
Client Setup Information
Additional context
If you deactivations user that not an owner of any chat - it's OK.
So the problem is in changing owner in chat to another user
Relevant logs:
The text was updated successfully, but these errors were encountered: