Loading Profile...
the latest version for chrome (aviator) is interferring with disconnect. here is the message i get from disconnect....
Warning:
This extension failed to redirect a network request to about:blank because another extension (mlomiejdfkolichcflejclcbmpeaniij) redirected it to data:application/javascript;base64,RkI9e2FwaTpmdW5jdGlvbigpe30sdWk6ZnVuY3Rpb24oKXt9LEV2ZW50OntzdWJzY3JpYmU6ZnVuY3Rpb24oKXt9fSxVSVNlcnZlcjp7fSxYRkJNTDp7cGFyc2U6ZnVuY3Rpb24oKXt9fSxpbml0OmZ1bmN0aW9uKCl7fSxfX25vU3VjaE1ldGhvZF9fOmZ1bmN0aW9uKCl7fX07.
i can not disable disconnect.
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
Official
Response
-
EMPLOYEE
1Ok, so this is a situation where both extensions are trying to do the same thing. Both extensions see that a request is going out to, for example, "http://somewebsite.com/might_be_a_tra...". When they see that this is happening, both extensions determine whether it's a tracker/ad and then block it. If one extension blocks or redirects the request before the other extension, you will get this error since the request has already been dealt with.
It's not really one extension or the other's fault. I think Ghostery is just getting the blame for the error here because it is verifying that the request is a tracker faster than the other extensions. Therefore it is redirecting the request first and causing the error in the other extension.
So maybe it's not Ghostery that you should be removing but the other extensions :)
But seriously, you should probably just ignore it if it's only displaying a little error message on the extensions page. If it was popping up an error message box or something then it would be a bigger issue.
P.S. for anyone wondering why we are redirecting to data:application/javascript;base64,KADK....: This is just encoded javascript. It contains fake javascript so that the page thinks that it successfully got the tracking script, but it really just got a script that does nothing. It helps unbreak some pages that would normally break when blocked by Ghostery.
-
Hi There,
Thanks for using Ghostery!
We're both trying to block the request by redirecting it. Disconnect is redirecting to about:blank, which is nothing. We are redirecting to a surrogate script, which is actually better.
the "data:application/javascript..." is more useful than "about:blank" that disconnect is redirecting to.
Hope that helpsComment- view 2 more comments
-
-
-
DJ Footprint March 16, 2015 00:55Hi Pete, DJ Footprint here. I'm having the exact same problem as Quinn - the 'Extension Error' - and the multiple string of random numbers/letters. 'Blur' (formerly DoNotTrackMe) simply suggested stopping using Ghostery - which i very much don't want to do. Can you come up with some advice, suggestions - anything?! My e-mail is shown below if you could contact me. This 'Extension Error' - and dealing with it is driving me nuts!EditDeleteRemove
-
-
Pete (Senior Communications Manager) March 16, 2015 13:17Heh.. totally.. I asked our developer to respond with some more technical information for you. I hope that will help your and everyones issue with this. Sorry again for the inconvenience.EditDeleteRemove
-
-
-
-
I’m
scared someday the internet will collapse on itself
This reply was created from a merged topic originally titled Conflict with Disconnect.
When I start Chrome on OS X with both Ghostery and Disconnect installed, I see the following error:
This extension failed to redirect a network request to about:blank because another extension (Ghostery) redirected it to data:application/javascript;base64...
(Screenshot of this at .)
Suggestions?
-
-
I’m
confused
This reply was created from a merged topic originally titled Corresponded with 'Blur' (formerly DoNotTrackMe) - Their 'suggestion'? - stop usi....
I am repeatedly receiving an 'Extension Error' - whereby Ghostery is not sending (or interracting) properly with 'Blur' (another extension i have). I'm repeatedly getting 3 orange bars at the top-right of my Chrome Browser (running on a Windows 8.1 Laptop) - with Chrome as my main browser. At the side of each Ad-Blocker, there is a very, very long string of numbers and letters - and the message that Ghostery is not re-directing Java-Script information. - I'm a 'novice' - and also suffering from long-term debilitating very, very painful physical illnesses - which make matters such as this difficult to deal with / comprehend. Please help or assist if possible! Many Thanks! - DJ Footprint @ ja.footprint@gmail.com -
-
I’m
frustrated
Could someone - Pete maybe? - get in touch with Google/Chrome - and sort this problem out? Please?
DJ Footprint. -
-
EMPLOYEE
1Ok, so this is a situation where both extensions are trying to do the same thing. Both extensions see that a request is going out to, for example, "http://somewebsite.com/might_be_a_tra...". When they see that this is happening, both extensions determine whether it's a tracker/ad and then block it. If one extension blocks or redirects the request before the other extension, you will get this error since the request has already been dealt with.
It's not really one extension or the other's fault. I think Ghostery is just getting the blame for the error here because it is verifying that the request is a tracker faster than the other extensions. Therefore it is redirecting the request first and causing the error in the other extension.
So maybe it's not Ghostery that you should be removing but the other extensions :)
But seriously, you should probably just ignore it if it's only displaying a little error message on the extensions page. If it was popping up an error message box or something then it would be a bigger issue.
P.S. for anyone wondering why we are redirecting to data:application/javascript;base64,KADK....: This is just encoded javascript. It contains fake javascript so that the page thinks that it successfully got the tracking script, but it really just got a script that does nothing. It helps unbreak some pages that would normally break when blocked by Ghostery. -
EMPLOYEE
