Hi! Please, try updating to the latest version of Safari (Safari 6), clear your browsing cache, and check whether there’s still a problem tweeting through our buttons. Let me know how this goes. Thanks!
Yes it is. PC I can only do 5.1.7. My client owns a Mac though and has the latest Safari 6 version. Same thing. On my safari here, it does the same thing for every shareaholic plugin site that is posted in the “reviews/ratings” section as well, so I would either assume its a safari issue.
@raithedavion have you tried clearing your browser cache?
Yes. Same result afterward.
I am having the same problem with Safari latest version. Specifically with the twitter share button.
Here is some more information for you.
Safari V5.17
INVALID_STATE_ERR: DOM Exception 11: An attempt was made to use an object that is not, or is no longer, usable. shareaholic_tools.js:166
TypeError: ‘undefined’ is not a constructor (evaluating ‘new f.prototype.Bookmarklet(b)’) shareaholic.js:289
I also have had complaints with users having google chrome. However, I don’t know the version.
@camdenz can you please try clearing your browser cache and trying again?
We’ve been rolling out a number of enhancements to Shareaholic lately. Our JavaScript code can get cached locally in your browser for up to 2 days (for better performance). Deleting your browser cache will ensure you’re running the latest script. If the issue continues after clearing your browser cache, please let us know! Also, ensure you’re running the latest version of the plugin (v6.1.3.8)
Plugin Version 6.1.3.8
Cleared browser cache multiple times, safari version 5.1.7 on windows 7
Hmmm, same issue here. When we use the twitter share option the ‘loading bookmarklet’ message stays on the screen. Using latest versions of Chrome and Safari on Mac. Cleared caches and everything …
Same issue here, using a Mac. Firefox seems to work, but that’s it. Caches have been cleared multiple times.
Anyone having trouble with the bookmarklet loading, please contact us through our support center with your site’s URL and a description of the problem so that we can collect more information and add you to an open ticket concerning this issue. Thanks!
