With 'Created subfolder' aka 'Keep top-level folder' disabled, save_path doesn't actually point to the actual storage location if the user manually changed it to a subdirectory, but always points to some root folder.That's based on what people say, I haven't tested it.
#QBITTORRENT SONARR SETUP TORRENT#
Now with the new version, regardless of that option, the torrent content is put in save_path without a per-torrent subdirectory. This is the behavior that Sonarr&Radarr relied upon. In I'm probably saying a lot of wrong things, and I apologize.Ĭreate subfolder was renamed to Keep top-level folder, no functional difference there but there's also other commits that might be affecting it, specifically dc3d23c and 564d845 but I haven't studied them in detail.įrom what I understand there are two separate issues: If it was a single file torrent, wouldn't it be that folder anyways, instead of a subfolder? However, the Web API still has create subfolder:Īlso, I'm a tiny bit confused by your explanation, sorry do you mind giving an example? Single file torrents have always lived under the save directory you've picked, create subfolder doesn't seem to do anything (no matter if it's enabled or disabled - default is enabled.) on 4.2 for a single file torrent, or am I just missing the purpose of this ( create subfolder) option.?Īnd the save_path API item in the json returned is that folder so all files in the torrent are found in that folder and not a subfolder of the folder like before. the old option was fine, why did they change it!? (Obviously, I am an example of a user who is confused by it.) You're correct, it's 4.2.whatever the latest minor version is.
0 kommentar(er)
