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

Magnet auto add conflict with default folder set as "Same as torrent" #6794

Open
r0verchr0me opened this issue Apr 15, 2024 · 4 comments
Open

Comments

@r0verchr0me
Copy link

What is the issue?

The seems to be an issue with how the setting are working.

For example, i have set the default folder for downloading to be the same as the torrent file, with the Add Windows case unchecked, since the torrents files are being arranged and the automatically loaded into transmission, it works great.

However, when i click a magnet link the Add Windows pops up asking me where to save the torrent.

I think you should make a separate setting of auto add, depending of the type, Magnet or torrent file.

Which application of Transmission?

macOS app

Which version of Transmission?

4.0.5 (a6fe2a6)

@killemov
Copy link

Where do you click on that magnet? On web page X? Can you then save the torrent and subsequent content to web page X? (Magnet->Torrent->Content, right?)
So if you then want to save all the resolved torrents, and contents, in a default folder, why not the regular torrents as well?
So works as designed.

@r0verchr0me
Copy link
Author

A lot of trackers work with magnet link only, thus it only the magnet link.

@killemov
Copy link

Again, where do you click on that magnet? Is it a place where you can store a torrent or is it a web page where you can't? What happens if you click on an actual torrent on a web page?

@r0verchr0me
Copy link
Author

All of the times, magnet are links in a webpage. Thus there should be an option to where to store the torrent of the magnet link.

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

No branches or pull requests

2 participants