You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that prior to v4.1.3, qbit_manage exposed configuration options such as ignoreTags_OnUpdate and force_retag_all.
From what I can tell, these options no longer exist, and I could not find any documentation describing what replaced them (if anything).
My questions are:
How are we now supposed to force re-tagging for certain tags (e.g. no.hardlink, issue, update)?
Are there any tags that are automatically re-processed on subsequent runs, or is tagging still strictly “one-shot”?
Is manual tag removal in the qBittorrent WebUI now the only supported way to trigger re-tagging?
Context / use case:
This is my first time configuring qbit_manage. Initially, I forgot to include some trackers in the trackers config section.
As expected, torrents from those trackers were tagged with my fallback tag (# update).
After adding the missing trackers to the configuration, these torrents are not re-tagged on subsequent runs. I understand that manually removing the tag in the qBittorrent WebUI and re-running qbit_manage works, but I was wondering whether there is now an equivalent built-in mechanism (similar to what existed before 4.1.3) to handle this automatically.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that prior to v4.1.3, qbit_manage exposed configuration options such as
ignoreTags_OnUpdateandforce_retag_all.From what I can tell, these options no longer exist, and I could not find any documentation describing what replaced them (if anything).
My questions are:
no.hardlink,issue,update)?Context / use case:
This is my first time configuring qbit_manage. Initially, I forgot to include some trackers in the
trackersconfig section.As expected, torrents from those trackers were tagged with my fallback tag (
# update).After adding the missing trackers to the configuration, these torrents are not re-tagged on subsequent runs. I understand that manually removing the tag in the qBittorrent WebUI and re-running qbit_manage works, but I was wondering whether there is now an equivalent built-in mechanism (similar to what existed before 4.1.3) to handle this automatically.
Beta Was this translation helpful? Give feedback.
All reactions