starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Option to NOT create folder based on torrent name (also in import torrents) #4010

New issue

Closed

opened 2026-02-21 17:05:05 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-21 17:05:05 -05:00

Owner

Originally created by @NULUSIOS on GitHub (Mar 4, 2016).

There is no option to put torrent contents directly to the path chosen by the user. In other words NOT create a folder with the name of the torrent.

Some people seed torrents from specific places (or from where they -read-only- use them also) and don't want the contents placed in folders mandated by the torrent name. Sometimes torrents are named with a name that suits only the torrent maker, or sometimes between torrent updates, they change the name of the torrent, so someone needs to take extra actions (rename things) to partially-seed and download remaining contents of the update.

I really want to move to qBittorrent (instead of the other popular client with so many problems) but this really puts a stop.

Originally created by @NULUSIOS on GitHub (Mar 4, 2016). There is no option to put torrent contents directly to the path chosen by the user. In other words NOT create a folder with the name of the torrent. Some people seed torrents from specific places (or from where they -read-only- use them also) and don't want the contents placed in folders mandated by the torrent name. Sometimes torrents are named with a name that suits only the torrent maker, or sometimes between torrent updates, they change the name of the torrent, so someone needs to take extra actions (rename things) to partially-seed and download remaining contents of the update. I really want to move to qBittorrent (instead of the other popular client with so many problems) but this really puts a stop.

deekerman closed this issue

2026-02-21 17:05:08 -05:00

deekerman commented

2026-02-21 17:05:10 -05:00

Author

Owner

@thalieht commented on GitHub (Mar 4, 2016):

#588 duplicate

@thalieht commented on GitHub (Mar 4, 2016): #588 duplicate

deekerman commented

2026-02-21 17:05:10 -05:00

Author

Owner

@NULUSIOS commented on GitHub (Mar 4, 2016):

Seems this is going to be closed (after I read #588).

We need to add though, that NOT implementing this breaks proper import of torrents completed by other clients. They are considered empty and download from scratch.

Using the import function does not allow (the workaround) renaming of top folder, so the user has to rename the folder in the actual disk, thus breaking their setup.

@NULUSIOS commented on GitHub (Mar 4, 2016): Seems this is going to be closed (after I read #588). We need to add though, that NOT implementing this breaks proper import of torrents completed by other clients. They are considered empty and download from scratch. Using the import function does not allow (the workaround) renaming of top folder, so the user has to rename the folder in the actual disk, thus breaking their setup.

deekerman commented

2026-02-21 17:05:10 -05:00

Author

Owner

@DrKittens commented on GitHub (Mar 4, 2016):

Actually theres an active PR in the works to add in this functionality already.
https://github.com/qbittorrent/qBittorrent/pull/4081

They've just been having a few issues with the libtorrent side of things afaik,
Currently that PR is in the milestone for the next release along with streaming optimisations 👍

Idk its current status because glassez is currently doing something with the saving management and that may/may not conflict with it (havent been bored enough to read glassez's code because its incomplete and not a feature i've been interested in cloning in early to my version)

As for closing this you can actually close the issue yourself :)

@DrKittens commented on GitHub (Mar 4, 2016): Actually theres an active PR in the works to add in this functionality already. https://github.com/qbittorrent/qBittorrent/pull/4081 They've just been having a few issues with the libtorrent side of things afaik, Currently that PR is in the milestone for the next release along with streaming optimisations :+1: Idk its current status because glassez is currently doing something with the saving management and that may/may not conflict with it (havent been bored enough to read glassez's code because its incomplete and not a feature i've been interested in cloning in early to my version) As for closing this you can actually close the issue yourself :)

deekerman commented

2026-02-21 17:05:10 -05:00

Author

Owner

@NULUSIOS commented on GitHub (Mar 4, 2016):

I don't want to close it, because the other PR do not mention adding this functionality also in import function.

@NULUSIOS commented on GitHub (Mar 4, 2016): I don't want to close it, because the other PR do not mention adding this functionality also in import function.

deekerman commented

2026-02-21 17:05:10 -05:00

Author

Owner

@DrKittens commented on GitHub (Mar 4, 2016):

Good point, you are correct it does not!
May want to instead rename this to reflect that (so its no longer a dupe of 588) and/or post in the linked 4081 PR to ask/confirm if the change it makes is global and affects the import torrent function.
👍

@DrKittens commented on GitHub (Mar 4, 2016): Good point, you are correct it does not! May want to instead rename this to reflect that (so its no longer a dupe of 588) and/or post in the linked 4081 PR to ask/confirm if the change it makes is global and affects the import torrent function. :+1:

deekerman commented

2026-02-21 17:05:10 -05:00

Author

Owner

@NULUSIOS commented on GitHub (Mar 4, 2016):

I did the title change and this thread is also referenced in 4081 already, so I don't think I need to do anything about that.

@NULUSIOS commented on GitHub (Mar 4, 2016): I did the title change and this thread is also referenced in 4081 already, so I don't think I need to do anything about that.

deekerman commented

2026-02-21 17:05:10 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Apr 17, 2017):

Implemented by #5465. It will appear in v3.4.0.

@sledgehammer999 commented on GitHub (Apr 17, 2017): Implemented by #5465. It will appear in v3.4.0.