i.e. something.*.HDTV.XviD* seems to be interpreted as *something.*.HDTV.XviD*, resulting in SABnzbd occasionally downloading things it shouldn't - especially series with a single common word as the title.
Note: I *just* installed 0.5.1 RC1, but the changelog doesn't mention anything like this, so I assume it's still there
RSS feeds: no wildcard at start still interpreted as wildcard
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: RSS feeds: no wildcard at start still interpreted as wildcard
Yes it is.
If you don't want that you'll have to use a real regular expression.
See: http://wiki.sabnzbd.org/configure-rss-v2 section "Regular expressions".
If you don't want that you'll have to use a real regular expression.
See: http://wiki.sabnzbd.org/configure-rss-v2 section "Regular expressions".
Re: RSS feeds: no wildcard at start still interpreted as wildcard
Didn't realise that! For reference:
Would be nice if a future version interprets the lack of a non-regex wildcard at the start, the same way it interprets the lack of one at the end, thoughre:^something.something.*HDTV.XviD.*
Re: RSS feeds: no wildcard at start still interpreted as wildcard
No, because it's been like this since we introduced RSS feeds (two years ago).
If we change that, people's current filters would suddenly start acting different.
If we change that, people's current filters would suddenly start acting different.