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

[RSS Dowloader] Using "set as default save path" should not interfere with rss downloader rules #2857

Closed
Matth7878 opened this issue Apr 10, 2015 · 1 comment
Labels
autoCloseOldIssue RSS RSS-related issues/changes

Comments

@Matth7878
Copy link

Sorry If I'm not clear but I think there's a problem with set as default path in add dialog and RSS downloader rules using save to a different directoy :

  • let's say default path is c:\torrent
  • set a rss rule to download using a different directory : c:\torrent\movie
  • download a torrent, use c:\torrent\movie and check "set as default save path"
  • now the rss rule has lost it's setting to use a different directory (which doesn't matter since it's the same as default save path)
  • now download another torrent and use c:\torrent and check "set as default save path"
  • look at the rss rule : save to a different directory is still uncheck and do not respect what the rule was set to do

I think "set as default save path" in the add torrent dialog should not reset "different directory" preference from rss rules even though it become the same as the default save path. It will ensure that future change will not end in auto downloading in wrong directories.

@sledgehammer999
Copy link
Member

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@qbittorrent qbittorrent locked and limited conversation to collaborators Oct 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
autoCloseOldIssue RSS RSS-related issues/changes
Projects
None yet
Development

No branches or pull requests

2 participants