Page 2 of 3

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Tue Mar 06, 2012 2:24 am
by BobbyPhoenix
tablo wrote:
BobbyPhoenix wrote:I had the same issue on 19. I found that removing, or uninstalling the extension, and then re-downloading it gives a new menu. You no longer have a list with check boxes of what is active with a version/last updated to the right, but instead you have a dropdown box with the ability to choose what filters you want. The ones active are highlighted to show which ones you have working.
I don't know what you mean because I haven't been able to get that new look. Screenshot?
This is all I have now. My filters just show highlighted. http://i572.photobucket.com/albums/ss16 ... chrome.jpg

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Tue Mar 06, 2012 9:11 am
by dicks
I moved back to FF11b6. Problem solved ;) :D

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Tue Mar 06, 2012 11:14 pm
by Guest
BobbyPhoenix wrote:
tablo wrote:
BobbyPhoenix wrote:I had the same issue on 19. I found that removing, or uninstalling the extension, and then re-downloading it gives a new menu. You no longer have a list with check boxes of what is active with a version/last updated to the right, but instead you have a dropdown box with the ability to choose what filters you want. The ones active are highlighted to show which ones you have working.
I don't know what you mean because I haven't been able to get that new look. Screenshot?
This is all I have now. My filters just show highlighted. http://i572.photobucket.com/albums/ss16 ... chrome.jpg
Oh, that's because the filters "disappeared" as part of this bug, that's not a new look. The highlighted filters are the "main" filters, since there are regional variants of EasyList and Fanboy's List right below it.
dicks wrote:I moved back to FF11b6. Problem solved ;) :D
I'll be using Firefox Nightly I guess. Sometimes the ads won't even block because of this bug. :roll:

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Wed Mar 07, 2012 12:23 am
by 123Guest
I was having this issue with the experimental ABP and Chrome Dev 19.0.1049.3 and 19.1055.1

I removed the experimental version of ABP and I am now running the beta ABP 1.2 with the same issues.

Is this a Chrome Dev browser issue or an issue with ABP? or do I need to totally remove the browser and do a fresh install??

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Wed Mar 07, 2012 6:53 am
by 1Guest
It's an issue with ABP. lewisje, who's a great forum contributer, said on the previous page that Palant concentrates on supporting the stable version. I don't know why it can't support all versions, Adblock for Chrome doesn't exhibit this problem. This bug will be hitting the beta channel soon where there's possibly millions of users. Anyway, what I've done, at least for now, is uninstall ABP and am now using Adblock for Chrome which works just as good.

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Wed Mar 07, 2012 1:26 pm
by gugarci
iron2000 wrote:Still on Chrome 17 with latest ABP dev build, experiencing the same problem too.
Found that my filters are still dated January 21, just did a manual update.
Me too, I just started a new thread. But I'm no longer using an experimental build. I was before Chrome 17
came out.

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Sat Mar 10, 2012 5:33 am
by lewisje
^^My suspicion is that Palant is actually trying to figure out what's causing the problem and for now is sending bug reports to the Chromium project rather than trying to work around the problems in an inherently unstable product, much as he does with Mozilla when problems with Adblock Plus are found in Nightly; he is a bit hampered at the moment by the lack of an Issue Reporter in the Chrome extension.

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Sun Mar 11, 2012 9:11 am
by funnyb
I have same bug in latest Chrome dev.

p.s.

I did not create a new thread, just want to ask about the update channel of Adblockplus for Chrome.
To get true network blocking like ff, istead of element hiding, still need to use experemental Adblockplus and need to enable experemental extensions api Chrome flag?
Or its already on stable Chrome, and stable Webstore Adblockplus?

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Sun Mar 11, 2012 9:35 am
by mapx
it is real blocking (if you have at least chrome 17) - you can disable the experimental api flag

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Sun Mar 11, 2012 2:07 pm
by majaji
Hi,

can somebody already say, when Adblock Plus comes out final, with the new webRequest API?

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Sun Mar 11, 2012 2:14 pm
by mapx
majaji wrote:Hi,

can somebody already say, when Adblock Plus comes out final, with the new webRequest API?
already using "the new webRequest API"

releases/adblock-plus-12-beta-for-googl ... e-released

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Sun Mar 11, 2012 5:01 pm
by majaji
mapx wrote: already using "the new webRequest API"

releases/adblock-plus-12-beta-for-googl ... e-released
Ah, great, thanks.

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Thu Mar 15, 2012 8:59 am
by dimsumwonder
I have the same issue as well, on 19.0.1068.0 dev-m. I thought it was an issue only for me but I suppose not. Ads are still blocked though.

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Thu Mar 15, 2012 10:17 am
by adam777
ABP is pretty much unusable on Chromium (and Chrome 19) these days.
I'm experiencing all that was mentioned here and on other threads (Subscriptions goes missing, filters not getting updated, ABP seems to work or not work in random on each launch etc.)
I moved to AdBlock for the time being.

Re: New Chrome Dev 19.0.1049.3 Filters no longer update

Posted: Thu Mar 15, 2012 12:47 pm
by Wladimir Palant
Fixed this issue: https://hg.adblockplus.org/adblockplusc ... 4e3d442094. New development build will be out in a few minutes, it should work fine.

Turned out to be caused by http://crbug.com/115714.