You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding a new torrent via web-ui and then using "rename" or using "rename" in the "Add new torrent" dialog then this does not reflect for the top-level directory.
What is the expected behavior
Expected behavior is to actually rename the directory too - currently only torrent in the transfers list will be renamed, but directory name will be preserved as is.
Steps to reproduce
Just download some torrent using web-UI and use rename functionality by either right-clicking on the download or when adding new torrent.
Extra info(if any)
I can see that api call to /rename is done successfully with HTTP response code 200 and I can see torrent getting renamed in the web-UI list, but I can't see anything regarding rename in the log files nor do I see it getting renamed on the actual disk.
The text was updated successfully, but these errors were encountered:
Please provide the following information
qBittorrent version and Operating System
qBittorrent v4.1.8, FreeBSD
What is the problem
When adding a new torrent via web-ui and then using "rename" or using "rename" in the "Add new torrent" dialog then this does not reflect for the top-level directory.
What is the expected behavior
Expected behavior is to actually rename the directory too - currently only torrent in the transfers list will be renamed, but directory name will be preserved as is.
Steps to reproduce
Just download some torrent using web-UI and use rename functionality by either right-clicking on the download or when adding new torrent.
Extra info(if any)
I can see that api call to
/rename
is done successfully with HTTP response code 200 and I can see torrent getting renamed in the web-UI list, but I can't see anything regarding rename in the log files nor do I see it getting renamed on the actual disk.The text was updated successfully, but these errors were encountered: