Regexp broken, this time for real.

[tharrison1]

To beef up my security filters, I did a search for "foo bar" audio, so that every result would be guaranteed to be spam. What slipped through my existing filters was this:

foo bar [club mix].mp3
08 - foo bar.mp3
08 - foo bar.mp3
08 - foo bar.mp3

Now, the 08s I can't do anything about without false positives but I should be able to safely get rid of the first one with

.*( [club mix]\.mp3)$

right?

Wrong. No apparent effect at all. Okay, maybe square brackets need escaping?

.*( \[club mix\]\.mp3)$

Still nothing.

What's up with that?

[cyko_01]

[tharrison1]

Neither change has any effect.

[cyko_01]

[tharrison1]

Security window, and reg exp is checked.

[tharrison1]

Here's another one that should work, but doesn't:

^(Crack for - ).*(\.zip)$

"Crack for - foo bar.zip" doesn't get removed by this, but should.

[old_death]

I'm not sure whether a change to the security window content is directly applied to the content of the search window. You might want to try to use the search filter to test your regEX code and afterwards add it to your security window. Then, the results shouldn't show up anymore the next time you do that search.

[tharrison1]

It does apply immediately to searches that are open.

[cyko_01]

[old_death]

Is there a bug report for this?

[cyko_01]