Skip to content
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

webUI does not rename directory on rename action #11512

Closed
jarmo opened this issue Nov 24, 2019 · 1 comment
Closed

webUI does not rename directory on rename action #11512

jarmo opened this issue Nov 24, 2019 · 1 comment
Labels
WebUI WebUI-related issues/changes

Comments

@jarmo
Copy link

jarmo commented Nov 24, 2019

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.

@FranciscoPombal FranciscoPombal added the WebUI WebUI-related issues/changes label Feb 19, 2020
@luzpaz
Copy link
Contributor

luzpaz commented Feb 19, 2024

Closing.

@luzpaz luzpaz closed this as not planned Won't fix, can't repro, duplicate, stale Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WebUI WebUI-related issues/changes
Projects
None yet
Development

No branches or pull requests

3 participants