Code: Select all
||google-analytics.com^$third-partygoogle-analytics.com (EasyPrivacy)
-
Guest
- Guest
google-analytics.com (EasyPrivacy)
Why does
not on EasyPrivacy?
-
Guest
- Guest
Can you provide an example where it breaks site functionality?
Any site listed as a domain exception in the old filter had a problem with Google Analytics being blocked:
However, potentially any site could have issues due to the errors that occurred as a result of blocking the scripts.
Code: Select all
.google-analytics.com/$domain=~asos.com|~beatport.com|~britannica.com|~catalog.belkin.com|
~crushorflush.com|~designer.userbars.com|~expotv.com|~forex.com|~gamepro.com|
~gmodules.com|~jonathancoulton.com|~krone.tv|~minyanville.com|~oasisactive.com|
~reiseplanung.de|~sirius.com|~smash247.com|~songza.com|~tangle.com|~typeracer.com|
~yestosafesex.com-
Guest
- Guest
can you provide a more detailed example: I mean a link to a page of one of these website + writing what's not working when it's blocked.
You were actually given a hep of domains to look at and make sure we are not telling lies !!
Let me try to clear it up:
.google-analytics.com/
Was used to block google-analytics.
Reports started coming in about sites no working properly (mainly videos I think)
The filter was modified so that it would exclude certain sites (domain exceptions)
The domain switch can be used in 2 ways. To make a filter only work on a given domain or to make the filter work on everywhere except a given domain (that's what the ~ does).
So if you try visiting some of the sites that were listed as domain exceptions+
I'm pretty sure this is accurate but someone will correct me if not.
Let me try to clear it up:
.google-analytics.com/
Was used to block google-analytics.
Reports started coming in about sites no working properly (mainly videos I think)
The filter was modified so that it would exclude certain sites (domain exceptions)
The domain switch can be used in 2 ways. To make a filter only work on a given domain or to make the filter work on everywhere except a given domain (that's what the ~ does).
So if you try visiting some of the sites that were listed as domain exceptions+
you should soon run into trouble (remove the ~ and add www. to the list of domains above).asos.com|~beatport.com|~britannica.com|~catalog.belkin.com|
~crushorflush.com|~designer.userbars.com|~expotv.com|~forex.com|~gamepro.com|
~gmodules.com|~jonathancoulton.com|~krone.tv|~minyanville.com|~oasisactive.com|
~reiseplanung.de|~sirius.com|~smash247.com|~songza.com|~tangle.com|~typeracer.com|
~yestosafesex.com
I'm pretty sure this is accurate but someone will correct me if not.
If you really want to see the problems reported on each of the sites I would recommend searching the forum. Below are links to a few of the issues that were raised:
http://www.typeracer.com - Firefox freezes
http://www.asos.com - Flash doesn't load
http://www.crushorflush.com - users can't edit their profile
http://www.designer.userbars.com - the designer fails to load
However, the primary reason that Google Analytics was removed was not due to the excessive number of domain exceptions that had to be applied, but was due to the fact that, because of the function that was left undefined and the consequent error message that occurred as a result of blocking the script, there could potentially be problems with any site using the service. What we have seen on this forum is most probably the tip of a very large iceberg.
If you are still worried about the consequences of the decision I would recommend reading Erunno's post on the limited risks involved; it is located here.
http://www.typeracer.com - Firefox freezes
http://www.asos.com - Flash doesn't load
http://www.crushorflush.com - users can't edit their profile
http://www.designer.userbars.com - the designer fails to load
However, the primary reason that Google Analytics was removed was not due to the excessive number of domain exceptions that had to be applied, but was due to the fact that, because of the function that was left undefined and the consequent error message that occurred as a result of blocking the script, there could potentially be problems with any site using the service. What we have seen on this forum is most probably the tip of a very large iceberg.
If you are still worried about the consequences of the decision I would recommend reading Erunno's post on the limited risks involved; it is located here.