We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The delete button on users is broken. It shows as clickable, but nothing happens.
What version of Overseerr are you running? 1.6.0
You can find it under: Settings -> About -> Version
To Reproduce Steps to reproduce the behavior:
Expected behavior User deletion should proceed. Perhaps a confirmation?
Screenshots None needed. No error.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Related: I don't think the 'Delete' button should be visible on the same user that is currently logged in.
The text was updated successfully, but these errors were encountered:
Not broken, but not implemented. Will get it added! Thanks for making the issue!
Sorry, something went wrong.
Thank you for the response! And anytime! I'm loving this project!
727fa06
🎉 This issue has been resolved in version 1.9.0 🎉
The release is available on v1.9.0
v1.9.0
Your semantic-release bot 📦🚀
No branches or pull requests
Describe the bug
The delete button on users is broken. It shows as clickable, but nothing happens.
What version of Overseerr are you running?
1.6.0
You can find it under: Settings -> About -> Version
To Reproduce
Steps to reproduce the behavior:
Expected behavior
User deletion should proceed. Perhaps a confirmation?
Screenshots
None needed. No error.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Related: I don't think the 'Delete' button should be visible on the same user that is currently logged in.
The text was updated successfully, but these errors were encountered: