Bad UX of changing save location of multiple torrents. #2680

Closed
opened 2026-02-21 16:21:16 -05:00 by deekerman · 6 comments
Owner

Originally created by @yurikoles on GitHub (Jun 22, 2015).

For example one have downloaded all torrents to one folder. Then changed folder's name or path manually by another program. It's obvious to select all torrents than right-click=>"Set location..."=>choose new the folder. But it only changes location of first torrent in selected list.

Update: it actually changed location, but not offered me to check it. When I press "start", it downloads it again. And this Windows-style annoying dialog: "Do you really want to re-check selected torrent(-s)?"

Originally created by @yurikoles on GitHub (Jun 22, 2015). For example one have downloaded all torrents to one folder. Then changed folder's name or path manually by another program. It's obvious to select all torrents than right-click=>"Set location..."=>choose new the folder. But it only changes location of first torrent in selected list. Update: it actually changed location, but not offered me to check it. When I press "start", it downloads it again. And this Windows-style annoying dialog: "Do you really want to re-check selected torrent(-s)?"
deekerman 2026-02-21 16:21:16 -05:00
Author
Owner

@SanderBouwhuis commented on GitHub (Jun 22, 2015):

I'm currently using uTorrent, but want to switch (possibly to qBittorrent). The possibility to mass-move files to other locations is a MUST for me. So, can qBittorrent move multiple torrents in one go to a specified directory?

Edit:
What I mean is : is moving multiple torrents at once a feature of qBittorrent which according to YuriKoles currently has a bug? Or isn't it available in qBittorrent at all?

@SanderBouwhuis commented on GitHub (Jun 22, 2015): I'm currently using uTorrent, but want to switch (possibly to qBittorrent). The possibility to mass-move files to other locations is a MUST for me. So, can qBittorrent move multiple torrents in one go to a specified directory? Edit: What I mean is : is moving multiple torrents at once a feature of qBittorrent which according to YuriKoles currently has a bug? Or isn't it available in qBittorrent at all?
Author
Owner

@yurikoles commented on GitHub (Jun 22, 2015):

@SanderBouwhuis Please read full comment. It is transferred, but you need also to select all the torrents, then recheck. But after that: resume them. 3 actions, dough.

@yurikoles commented on GitHub (Jun 22, 2015): @SanderBouwhuis Please read full comment. It is transferred, but you need also to select all the torrents, then recheck. But after that: resume them. 3 actions, dough.
Author
Owner

@SanderBouwhuis commented on GitHub (Jun 22, 2015):

Aha, ok. Great to hear the feature works. The rechecking seems ridiculous when you move a couple of terabytes of data (takes hours).
I hope this will be fixed.

@SanderBouwhuis commented on GitHub (Jun 22, 2015): Aha, ok. Great to hear the feature works. The rechecking seems ridiculous when you move a couple of terabytes of data (takes hours). I hope this will be fixed.
Author
Owner

@yurikoles commented on GitHub (Jun 22, 2015):

@SanderBouwhuis I moved data manually, not via qBittorrent GUI.

@yurikoles commented on GitHub (Jun 22, 2015): @SanderBouwhuis I moved data manually, not via qBittorrent GUI.
Author
Owner

@SanderBouwhuis commented on GitHub (Jun 22, 2015):

Aha, ok. You didn't mention that. Now I understand.

@SanderBouwhuis commented on GitHub (Jun 22, 2015): Aha, ok. You didn't mention that. Now I understand.
Author
Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#2680
No description provided.