-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Deactivate organization button is not disabled for regular users #16080
Comments
Hello @zulip/server-settings members, this issue was labeled with the "area: settings (admin/org)" label, so you may want to check it out! |
Yeah agreed it's a regression. |
@zulipbot claim |
We need to disable the deactivate organization button all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug. fixes zulip#16080
We need to disable the deactivate organization button all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug. fixes zulip#16080
We need to disable the deactivate organization button all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug. fixes zulip#16080
We need to disable the deactivate organization button for all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug. fixes zulip#16080
We need to disable the deactivate organization button for all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug by replacing `[disabled="disabled"]` with `[disabled]` since we are accessing ‘disabled’ as a property, not an attribute. fixes zulip#16080
We need to disable the deactivate organization button for all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug by replacing `[disabled="disabled"]` with `[disabled]` since we are accessing ‘disabled’ as a property, not an attribute. fixes zulip#16080
We need to disable the deactivate organization button for all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug by replacing `[disabled="disabled"]` with `[disabled]` since we are accessing ‘disabled’ as a property, not an attribute. Fixes zulip#16080
We need to disable the deactivate organization button for all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug by replacing `[disabled="disabled"]` with `[disabled]` since we are accessing ‘disabled’ as a property, not an attribute. Fixes zulip#16080
We need to disable the deactivate organization button for all other users other than owner But currently, we are showing deactivate button for regular users also. This commit fixes the bug by replacing `[disabled="disabled"]` with `[disabled]` since we are accessing ‘disabled’ as a property, not an attribute. Fixes zulip#16080
Hello @Jagansivam28, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days. You can reclaim this issue or claim any other issue by commenting Thanks for your contributions, and hope to see you again soon! |
Hi @timabbott and @Gittenburg, I am new to this community and was looking to contribute. |
@zulipbot claim |
Welcome to Zulip, @ligmitz! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip! Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site. See you on the other side (that is, the pull request side)! |
@zulipbot claim |
Welcome to Zulip, @mgshestko! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip! Here's some tips to get you off to a good start:
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site. See you on the other side (that is, the pull request side)! |
After carefully reviewing my assigned bug, I’ve determined that it’s been fixed by two earlier submission report. My open pull request should be closed. How should I proceed? @timabbott |
Hello @mgshestko, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 10 days. Are you still working on this issue? If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 4 days. If you've decided to work on something else, simply comment Thank you for your valuable contributions to Zulip! |
@zulipbot abandon |
@Gittenburg cannot reproduce? |
Closing as no longer reproducible (probably resolved). |
Can be reproduced at https://chat.zulip.org/#organization/organization-profile.
I think this is a regression ... I remember the button being disabled before.
The text was updated successfully, but these errors were encountered: