-
Notifications
You must be signed in to change notification settings - Fork 414
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
Delete Key does not prompt a "Remove Torrent" confirmation, even with the option checked in. #2596
Comments
I labeled this as an enhancement. We can add an option to display a confirmation box, when using the delete key on |
i have the same problem, with very old version 4.0.2 it works fine (default is confirmation enabled) and the setting for confirmation dialog for delete works as expected and in 4.2.8 it does not matter what the setting is it deletes without confirmation. is it known which is the last version where this deletion confirmation dialog works? edit: |
@FunThomas76 Could you go to |
it saves the state under settings -> general -> confirm when deleting but checked or not checked makes here no difference but the loved confirm dialog shows up when deleting with removing files |
Resolved in v5.0 releasing shortly. |
Please complete the following tasks.
Tell us about your environment
Web Broser: Brave 1.60.114
ruTorrent v4.2.6
OS: Debian Bulseye | 5.10.0-26
Tell us how you installed ruTorrent
I'm running ruTorrent next to rTorrent in the crazymax docker container
Describe the bug
When pressing delete with a torrent selected, the .torrent file and the downloaded files are deleted without a confirmation box. This happens even with the "Confirm when deleting torrents" option checked.
This does not happen when using the top menu bar, and it doesn't happen when using the right click menu provided with the Deletedata plugin.
Steps to reproduce
Expected behavior
The confirmation box with "Remove Torrent(s) : Do you really want to remove the selected torrent(s)?" should be shown before deleting.
Additional context
No response
The text was updated successfully, but these errors were encountered: