selecting folders in the search box downloads the entire folder instead of all the search items in that folder #11733

New issue

Closed

opened 2026-02-21 21:51:53 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 21:51:53 -05:00

Owner

Originally created by @as-muncher on GitHub (Feb 10, 2021).

Please provide the following information

qBittorrent version and Operating System

4.3.3 64 bit on Windows 20h2 x64 10.0.19042

If on linux, libtorrent-rasterbar and Qt version

(type here)

What is the problem

When I select a torrent, in the content tab, and in the search box I enter "jpg", for instance, and all the .jpg files show up, there is a check box beside the folder name containing the .jpg files, and when I select those folders, the entire folder gets downloaded including the .jpg files, instead of just the .jpg files in that folder.

What is the expected behavior

The expected behaviour is that when I select the checkbox next to the folder name containing the search items, that only the search items in that folder will be select for download, not the whole folder which may have much larger files which I didn't want to download. I want to be able to select ctrl-A to highlight all my search items, then checkmark them for download. If I have 300 .jpg files in one folder, plus 200 huge .mp4 files, since I've selected "jpg" in the search window, I want all the .jpg files to be selected for download, so I don't have to manually select them all, then right-click, and choose the download priority.

Steps to reproduce

Start downloading a large torrent that has folder(s) with .jpg files and .mp4 or .avi files or other like that. In the search box, type "jpg" without the quotation marks. When you select the checkbox next to the folder, then click the x in the search box in the content tab, you will see that all the files in that one folder that you selected are marked to be downloaded instead of just the .jpg files.

Extra info(if any)

(type here)

Originally created by @as-muncher on GitHub (Feb 10, 2021). **Please provide the following information** ### qBittorrent version and Operating System 4.3.3 64 bit on Windows 20h2 x64 10.0.19042 ### If on linux, libtorrent-rasterbar and Qt version (type here) ### What is the problem When I select a torrent, in the content tab, and in the search box I enter "jpg", for instance, and all the .jpg files show up, there is a check box beside the folder name containing the .jpg files, and when I select those folders, the entire folder gets downloaded including the .jpg files, instead of just the .jpg files in that folder. ### What is the expected behavior The expected behaviour is that when I select the checkbox next to the folder name containing the search items, that only the search items in that folder will be select for download, not the whole folder which may have much larger files which I didn't want to download. I want to be able to select ctrl-A to highlight all my search items, then checkmark them for download. If I have 300 .jpg files in one folder, plus 200 huge .mp4 files, since I've selected "jpg" in the search window, I want all the .jpg files to be selected for download, so I don't have to manually select them all, then right-click, and choose the download priority. ### Steps to reproduce Start downloading a large torrent that has folder(s) with .jpg files and .mp4 or .avi files or other like that. In the search box, type "jpg" without the quotation marks. When you select the checkbox next to the folder, then click the x in the search box in the content tab, you will see that all the files in that one folder that you selected are marked to be downloaded instead of just the .jpg files. ### Extra info(if any) (type here)

deekerman

2026-02-21 21:51:53 -05:00

closed this issue
added the
GUI
label

deekerman commented

2026-02-21 21:52:04 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 19, 2025):

This ticket has been closed.

Closure Reason: being "out-of-date", 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.
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.
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.
Thank you for your contribution(s).

@xavier2k6 commented on GitHub (Mar 19, 2025): ### This ticket has been closed. ____ **Closure Reason: being "out-of-date", 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. * 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. * 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. * Thank you for your contribution(s).

deekerman commented

2026-02-21 21:52:04 -05:00

Author

Owner

@as-muncher commented on GitHub (Mar 19, 2025):

@xavier2k6 Did you actually try to reproduce this problem? When I give a detailled example of how to reproduce the error, shouldn't you check it out for yourself?

@as-muncher commented on GitHub (Mar 19, 2025): @xavier2k6 Did you actually try to reproduce this problem? When I give a detailled example of how to reproduce the error, shouldn't you check it out for yourself?

deekerman commented

2026-02-21 21:52:04 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 19, 2025):

@as-muncher No I did not, I have no intention of going through every obsolete ticket & verifying/disproving everything....feel free to open a new ticket as stated above...

Apologies if you may have a gripe with that but I hope you can understand that the ticket tracker is filled with obsolete/in dead man's land etc.

Your ticket was from 4 years & had went no where........

@xavier2k6 commented on GitHub (Mar 19, 2025): @as-muncher No I did not, I have no intention of going through every obsolete ticket & verifying/disproving everything....feel free to open a new ticket as stated above... Apologies if you may have a gripe with that but I hope you can understand that the ticket tracker is filled with obsolete/in dead man's land etc. Your ticket was from 4 years & had went no where........