Quade wrote:- If you load a GOG, then only the GOG filter profile will be used
- if you load an individual group, it first checks to see if the filter is set for the group. It it is, it's used. If it's not, the parent (GOG) is checked and if it's filter is set it's used. This is for files added to the download list. By the time the file hits the download list, only the filename filters really apply to it. The subject filters are primarily used for the post lists. Automatic download mode, will make use if the subject filters to determine what gets added to the download list.
- NZB Files because they're not listed in groups, get their own filters. "NZB Load filter" and individual filters for each autoload folder.
Ok, all of this seems to follow the logical top-down I expected. I don't know what Dthor's adversion to that is but it would be the generally accepted flow for parent-child structures which is what I though GoG was. If you don't want parent affecting child, you explicitly set the value at the child level. This should be true of all Group settings and again was my understanding of how the GoG feature worked.
So if
Automatic download mode, will make use if the subject filters to determine what gets added to the download list.
where are those filters coming from, the GoG or the Group? Given the behavior you describe I'd expect GoG's filter if no Group level filter but most certainly is not the case based on what's happening for me. Instead auto-mode ques *everything* new in a group unless I explicitly set that filter on that group, the GoG filter is being ignored.
What I am doing is auto-mode grabbing NZB's for several groups based on a filter. Works fine if I explicitly set the filter on all groups.