Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-file torrents no longer download into a subfolder #669

Open
rmadsack opened this issue Jan 22, 2025 · 0 comments
Open

Multi-file torrents no longer download into a subfolder #669

rmadsack opened this issue Jan 22, 2025 · 0 comments

Comments

@rmadsack
Copy link

rmadsack commented Jan 22, 2025

What version are you using?
2.0.95

Wat OS are you running?
Debian 12

Are you using Docker or as a service?
Service in lxc container

Which debrid provider are you using?
Premiumize

Which downloader are you using?
Internal

Hello,

I’ve noticed an issue with rdt-client where multi-file torrents are no longer being downloaded into a subfolder within my designated download directory. Previously, when downloading a multi-file torrent, a subfolder named after the torrent would automatically be created, and the files would be stored inside that subfolder.

However, now all the files are being placed directly into the main download folder without a subfolder. This behavior seems to have changed recently, as it was working fine before.

This causes issues with applications like Sonarr, which expect files to follow a specific folder structure to process them automatically.

Steps to reproduce:

  1. Configure the rdt-client with a designated download folder.
  2. Download a multi-file torrent.
  3. Observe that no subfolder is created, and files are placed directly in the main download directory.

Expected behavior:
A subfolder should be created for multi-file torrents within the download directory, named after the torrent, with all files stored inside it.

Current behavior:
All files are saved directly into the main download folder without creating a subfolder.

Additional information:
I have checked the log files, but there are no unusual entries or errors related to this behavior.

Please let me know if this is an intended change or if there is a way to configure the client to restore the previous behavior.

Thank you for your support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant