Whitelisting Domain doesn't work for filters
Whitelisting Domain doesn't work for filters
Hey Guys.
Nice work I have to tell you all. I really appreciate the good work, but now stumbled upon a problem:
In the new AdBlock Version you can import remote filters and keep them pretty new. Nice feature so far. But: the whitelisting of Domains/Sites/etc. seems to be ignored from filters. My own AdBlock entries are overriden by whitelisting, but not the imported filters. I have to disable them to look on a few sites, which named their top-menu sth. like "banner". OK, I don't need to use these new filters, right. But they are pretty good work for all other sites, nicely filtering what I don't want to see. Only in these few cases it would be nice, if they would apply before the whitelisting (and therefore overridden by my whitelist entry) instead of coming after it.
Oh, sorting the filters in front or behind the whitelists don't change things. I checked it. A pity.
Thanks again, perhaps someone also came across this and has a handy solution other than disable the filter completely.
Greets
Grey
Nice work I have to tell you all. I really appreciate the good work, but now stumbled upon a problem:
In the new AdBlock Version you can import remote filters and keep them pretty new. Nice feature so far. But: the whitelisting of Domains/Sites/etc. seems to be ignored from filters. My own AdBlock entries are overriden by whitelisting, but not the imported filters. I have to disable them to look on a few sites, which named their top-menu sth. like "banner". OK, I don't need to use these new filters, right. But they are pretty good work for all other sites, nicely filtering what I don't want to see. Only in these few cases it would be nice, if they would apply before the whitelisting (and therefore overridden by my whitelist entry) instead of coming after it.
Oh, sorting the filters in front or behind the whitelists don't change things. I checked it. A pity.
Thanks again, perhaps someone also came across this and has a handy solution other than disable the filter completely.
Greets
Grey
That's not exactly true Dogg.IceDogg wrote:whitelist (personal or otherwise) shouldn't be over written by any other filter. That would void their whole purpose.
Regular AD filters will allow whitelisting, but any active ELEMENT-HIDING filters still hide the elements EVEN if the site has been whitelisted. Hopefully, Wladimir can fix this bug.
@ Grey:
All AD subscriptions WILL whitelist, but element hiding filters won't. I doesn't matter where they came from. You should just DISABLE the element filter string)s) for the site that you are having trouble with.
I don't exactly get you here. Disable the filter for the site? How so?All AD subscriptions WILL whitelist, but element hiding filters won't. I doesn't matter where they came from. You should just DISABLE the element filter string)s) for the site that you are having trouble with.
What I do have now is a whitelist rule starting with a @@ for the whole domain this problem happens. But how to disable a abonnement-filter for a single domain?
First, I assume that you are using Adblock Plus 0.7? In Adblock Plus 0.7 you can click off the green bullet next to a SINGLE filter string.
And what subscription filterlist. Are you using the EasyList and/or EasyElement filter(s)? If not, I won't be able to isolate your problem. You would then have to contact the person who makes your filterset.
AD (blocking) filter strings are in black text ... ELEMENT (hiding) strings are in dark blue text and contain # or ## in the string. The Element ones can override the whitelisting. Most usually start with the name of the site's address, so if you find a dark blue string that has your site's address in it, try clicking the green bullet to disable it (them) and hit APPLY.
And what subscription filterlist. Are you using the EasyList and/or EasyElement filter(s)? If not, I won't be able to isolate your problem. You would then have to contact the person who makes your filterset.
AD (blocking) filter strings are in black text ... ELEMENT (hiding) strings are in dark blue text and contain # or ## in the string. The Element ones can override the whitelisting. Most usually start with the name of the site's address, so if you find a dark blue string that has your site's address in it, try clicking the green bullet to disable it (them) and hit APPLY.
@ Grey:
I will try to isolate the culprit for you even if you are not using my filterset, but I'll need a link and what it is you are trying to see.
*Addition to the previous post:
All whitelist strings will show up in green text in your filter box.
I will try to isolate the culprit for you even if you are not using my filterset, but I'll need a link and what it is you are trying to see.
*Addition to the previous post:
All whitelist strings will show up in green text in your filter box.
Last edited by rick752 on Sun Jul 23, 2006 4:11 am, edited 1 time in total.
Ah, just wanted to make sure we are not speaking about other thingsFirst, I assume that you are using Adblock Plus 0.7? In Adblock Plus 0.7 you can click off the green bullet next to a SINGLE filter string.


If I may point out a site where yours could be better: the german IT-News Golem.de have some ads in between the bold first paragraph and the normal style first paragraph of every news. The filter of Dr.Evil nicely removes the gap which results by removing the ad, perhaps this could be added to EasyElement as well?

But thanks for pointing out disabling of single rules, did see it, but didn't thought about it


Grey
Edit: Oh, very nice of you wanting to check out the problem. If you want, have a look at http://wow.orion.sc/phpraid/ while having Dr.Evils Ruleset activated. It is the #*(banner) which causes the trouble.
'banner' alone is not a good rule ... too many false-positives.Grey wrote: If you want, have a look at http://wow.orion.sc/phpraid/ while having Dr.Evils Ruleset activated. It is the #*(banner) which causes the trouble.
ps: I don't do non-english sites. My filters are made for large global sites and the North American, English speaking sites. Using my filter(s) and a good German list would be your best bet.
You should tell Dr. Evil about your false-positive. I'm sure he would like to know about it. We all need input to make these things as trouble-free as humanly possible.

Again thanks for your input. Should have tracked it down sooner but that damn hot weather over here makes it hard to think about those little things. I'll try and let him know about that but I'm curious: Is it right, that these rule may override my global @@ whitelist? Shouldn't it have a lower priority? If I select "Deactivate on xyz.de" I would take it for granted, that it doesn't block the banner graphics
But perhaps this is the wished behavior, so no problem.
After that much help, I just had to register here
Bye,
Grey

After that much help, I just had to register here

Bye,
Grey
No problem, Grey. With Wladimir on vacation for a couple of more weeks, a lot of us are pitching in to try to help with problems here. We may not get it right, but ONE of us will figure it out eventually.
And you're right! I would think that whitelisting SHOULD override an element hide .... I'll have to ask Wladimir about that when he gets back.
That is one of the reasons why element hiding is so dangerous to do ... AND, it doesn't show up in the blockable items list either. This is the main reason why I offer TWO different filtersets ... a regular one for only normal ads (EasyList) ... and another optional one only for elements (EasyElement). That way you can turn one or the other off to check a problem (regular block or element hide problem).
ps ... Welcome aboard
And you're right! I would think that whitelisting SHOULD override an element hide .... I'll have to ask Wladimir about that when he gets back.
That is one of the reasons why element hiding is so dangerous to do ... AND, it doesn't show up in the blockable items list either. This is the main reason why I offer TWO different filtersets ... a regular one for only normal ads (EasyList) ... and another optional one only for elements (EasyElement). That way you can turn one or the other off to check a problem (regular block or element hide problem).
ps ... Welcome aboard

Well "banner" alone is not a good rule at all, because it will lead to a lot ofGrey wrote:It is the #*(banner) which causes the trouble.
false positives (as already pointed out). The best would be to report that as a
bug to the filter's author.
And as you can see at the #, this is an element hiding rule. Those cannot be overridden by whitelisting.