-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
qbittorrent not saving the torrent file when adding through WebUI without starting the torrent but saves in UI #9970
Comments
Do you really add .torrent file or just Magnet link? |
Good question. in both cases Magnet link. sorry for the confusion. |
qBittorrent can't save torrent file since there is no metadata until you start torrent. But "Add new torrent" dialog from Desktop UI preloads metadata for magnet links (unless you close it earlier). |
Yes should it follow the same method and either show a similar dialog/ call in Web UI or download the meta data without starting the torrent? |
I don't think it's that easy to implement. It seems that the cost-benefit ratio will be very low. @Piccirello? |
If showing the dialog is costly, at least save/ download the metadata/ torrent file automatically without starting the torrent? |
Why do you really need it? |
Thats the reason I need it. when you add though the WebUI there is no way to see the files or sizes in that magnet file till it starts downloading. it would be really great if the same functionality is available in API and downloads the torrent or at least lets you know the list of files and sizes. |
any further thoughts @glassez ? |
I'm not web developer so I can't implement GUI-like "Add new torrent" dialog in Web UI (we have no similar behavior even in case of adding .torrent files). |
Related to #19498 |
As the Title says, qbittorrent not saving the torrent file when adding through WebUI when the "Start Torrent" settings is turned off. But adding the same torrent through Desktop UI and unchecking the "Start Torrent" saves the torrent in Torrents folder.
The text was updated successfully, but these errors were encountered: