Loading Profile...
Twitter,
Facebook, or email.
Ghostery (Safari/Mac) stops working after two or three times!
I have installed Ghostery in Safari on my Mac twice now. Each time it works for two or three sites and then nothing. I have restared Safari but still nothing. The Ghostery icon is in Safari's tool bar, and Safari tells me it is installed and enabled but no bubbles - nothing! Am I doing something wrong?
-
Hi Patrick,
What happens when you click on the Ghostery icon after loading a page where something should have been found?
Could you give me some examples of pages on which Ghostery should have found something, but didn't?Comment -
-
Nothing happens when I click the Ghostery icon other than the icon getting darker.
The first time I visited http://brooks.blogs.nytimes.com/ Ghostery showed the bubble with 7 or 8 trackers. This was the second site I visited after installing Ghostery. A third site also worked, but after that nothing. Now hen I visit any site, including the above, it shows nothing. -
-
Hmm, I haven't run across this issue before. Sorry, this is going to get a little tricky.
Could you go to Safari's Preferences, click on the Advanced tab, mark "Show Develop menu in menu bar", then reload the nytimes.com page, click "Show Error Console" in Safari's Develop menu, and finally, click on Ghostery's toolbar button and paste any output you see in the error console here?
You could also take a screenshot of the console and attach it to this thread.
Which Safari version do you have, and what other extensions do you have installed?-
I am experiencing the exact same problem with Safari version 5.1. Ghostery is enabled but grayed out and unresponsive despite deinstalling and installing and deinstalling.
I have no other extensions installed. -
-
-
-
-
I'm running Safari Version 5.0.5 (6533.21.1).
No other extensions installed.
What you see in the Console was already there after the site was loaded. No additional stuff was added by clicking the Ghostery icon.
-
-
Thanks for the screenshot. I see that Ghostery's blocker.js breaks on line 237.
I haven't been able to reproduce this yet ... What is your Mac OS version?
I'll keep looking and will let you know what I find. Sorry for the trouble. -
-
Is JavaScript enabled in your Safari's Preferences (under the Security tab)?
-
-
Do you have PithHelmet, or any other SIMBL (http://en.wikipedia.org/wiki/SIMBL) plug-ins installed?
How about any toolbars (such as from Conduit)?-
To view installed plug-ins, click on Safari's Help menu and then click "Installed Plug-ins".
-
-
-
-
-
Hi Patrick,
There are several other very similar reports of Ghostery not working on 5.0.5 now:
* http://getsatisfaction.com/ghostery/t...
* http://getsatisfaction.com/ghostery/t...
Could you please install AdBlock from http://extensions.apple.com/ and see if it works for you, or if it breaks in a similar way to Ghostery?
You should get a walkthrough page from AdBlock right after installing it. -
-
Patrick,
This seems promising: http://code.google.com/p/adblockforch...
Try going to Safari Preferences' Security tab, unchecking Enable JavaScript, rechecking it and finally reinstalling Ghostery. -
-
Sorry about not replying earlier. We've been away. Here's an update:
1. Quite by chance I found a work-around for the original problem. If I opened a new tab, Ghostery started to work properly in it and all future tabs. So I just opened a new tab each morning and closed the original tab and Ghostery worked for quite a long time until.....
2. After several days the menubar icon disappeared but the balloon appeared normally for each web site.
3. Yes, JavaScript is enabled.
4. No, I do not have PithHelmet, or any other SIMBL plug-ins installed.
5. AdBlock seems to work.
6. Today I downloaded the latest Ghostery and it seems to be working fine (although I haven't quit and reopened Safari to see if I still need to open a new tab) -
-
Well, I'm sorry but I still need to do the tab thing. When I reopened Safari the balloon appeared, and occasionally (but not always) a red number in the icon, but clicking on the icon produced nothing. Opening a new tab solved the problem again.
-
-
Patrick,
Does upgrading to Safari 5.1 solve this problem? -
CHAMP
