When adding a torrent with multiple files (e.g. this), the parent directory for the torrent is not created. Instead the torrent's files are created in the directory specified by 'Destination'.
The torrent directory can be created with 'Set Download Location', but that leads me to another issue: When using 'Set Download Location' with move data ticked, the files are not moved. It appears they are copied. It also appears that this function starts the torrent even if the previous state was stopped.
Setup:
libtorrent-ps feature-bind (ebuild)
rtorrent-ps feature-bind (ebuild)
nginx running for reverse proxy: https://p.teknik.io/Raw/RJu6R
Flood config: https://p.teknik.io/Raw/IuIVk
rtorrent displays no errors, neither does npm nor client (Chromium 61.0.3133.0).
P.S. sorry for the multi-issue issue~
I observed the same issue since the "Base path" option has been added.
I downgraded to c095dadafd33da7de56adda77857ca0f96ccaea3, and track new issues since :wink:.
Sorry for the delay in this silly bug! (Silly in the sense of implementation... very very annoying in real life)
Hello, with commit 524a0796c9bcf95693f4f3fe0ae1ad8633441d47, this is broken again.
Sorry @hunti88, will take a look.
I confirm that parent directory is not created (making a mess in the root torrent folder), the Move data doesn't works, and even if you move files manually the Check Hash option is not working (see issue #537). Managing Torrents with multiple files is very painful because of those issues and this can lead into ratio drop on private trackers if a mistake make you download files twice. So I think this is a critical bug.
Also confirmed here