Interesting thing here is this is not happening in Firefox, only Chrome and another point to note is that a property called bodyText is now set to hidden visibility in Chrome, fine in firefox!
Update time. Looks like i'm not the only one with this, Sebastien has asked me to check a couple of things, one was checking if this Chrome extension was installed ( http://t.co/ivWXvIe70K ) - it is and another is running in incognito and although the initial error dissapears, I now get another one:
Uncaught TypeError: Object [object Object] has no method 'jQuery' UmbracoSpeechBubbleBackend.js:37
In ~/Umbraco/Js/UmbracoSpeechBubbleBackEnd.js change line 37 which should at this moment read: speechBubble.jQuery(".speechClose").show(); That should actually read: jQuery(".speechClose").show();
After you change that make sure to increase the version number in your ClientDependency.config file so the file gets processed again.
Thanks Simon, I saw the same issue by coincidence on one of our installations as well. But the odd thing is that I don't see it in my local environment but only on the production environment.
However I will of course try and do what the magnificent Sebastiaan Janssen suggests above :)
@Jan I think the problem only appears once <compilation debug="false">, that's when ClientDependencyHandler kicks in and that might trigger it. Anyway, let me know if it helps!
@Simon Good to know it also appears in debug mode. Come to think of it, that's not so surprising.
Chrome is notoriously good at a caching stuff a little too agressively, try hard reloading a few times (CTRL+Refresh or SHIFT+Refresh). Also when you have the dev tools open, click on the cog in the lower right corner and enable "Disable cache (while DevTools is open)" if it isn't already on.
Was obviously caused by the fact that the code says speechBubble.jQuery(".speechClose").show(); insread of jQuery(".speechClose").show();, you would agree with me right? speechBubble has not method jQuery.
So if you fixed that javascript then I don't get why it can give the same error, it should at least be a slightly different error.
One other trick I sometimes use: go to yoursite.local/Umbraco/Js/UmbracoSpeechBubbleBackEnd.js (replace yoursite.local with your own url) and check that line 37 does indeed read: jQuery(".speechClose").show(); without the speechBubble prefix. Hard-refresh it if it doesn't.
Again, this will only work with <compilation debug="true" /> so if that is set to false, make sure to increase the version number in ClientDependency.config.
@Simon could you perhaps try from a different machine? Or perhaps simply just reboot the machine you're currently using. Caching and Chrome can be a bitch sometimes! (I'm first going to try all of the above stuff tomorrow so don't know if it works).
Not the speech bubble one - that was only showing in Firefox and is now fixed as I mentioned, however the one posted here is still the rampant rabbit that is causing thousands of errors.
Aha! So: yes, your rich text editors are loading again because the javascript was actually fixed.
And no: there's nothing we can do about a browser plugin throwing errors. I just tried to load the backoffice for 4.7.1 with that plugin installed and it starts throwing the same errors. This is a security measure, possibly enabled in a recent version of Chrome and the only thing you can do about it (as far as I can tell from a quick google search) is disable the security measure in Chrome.
4.11.8 unsafe javascript error after upgrade from 4.11.6
Just upgraded a 4.11.6 install which did not have this error and am now getting the following error displayed.
Tried reinstalling 4.11.8 and same. Tried incrementing clientdependancy version and same. Any ideas?
Interesting thing here is this is not happening in Firefox, only Chrome and another point to note is that a property called bodyText is now set to hidden visibility in Chrome, fine in firefox!
Wondering if a chrome only bug then?
Update time. Looks like i'm not the only one with this, Sebastien has asked me to check a couple of things, one was checking if this Chrome extension was installed ( http://t.co/ivWXvIe70K ) - it is and another is running in incognito and although the initial error dissapears, I now get another one:
Uncaught TypeError: Object [object Object] has no method 'jQuery' UmbracoSpeechBubbleBackend.js:37
UmbracoSpeechBubble.ShowMessage UmbracoSpeechBubbleBackend.js:37
umbracoCheckUpgrade umbracoUpgradeChecker.js:12
E ScriptResource.axd:2
(anonymous function) ScriptResource.axd:2
d ScriptResource.axd:2
H.w.completed ScriptResource.axd:2
f._onReadyStateChange
Also in incognito the bodyText field now appears!
Just to narrow it down:
Chrome version Version 26.0.1410.64 m (Windows 7)
Packages wise: ucomponents, config tree, Return Value Contact Form, Robots.txt Editor, Fam Fam icons, Dewd
No custom code overriding backoffice stuff that I know of
Hey Simon,
I think I might have found the cause, try this:
In ~/Umbraco/Js/UmbracoSpeechBubbleBackEnd.js change line 37 which should at this moment read:
speechBubble.jQuery(".speechClose").show();
That should actually read:
jQuery(".speechClose").show();
After you change that make sure to increase the version number in your ClientDependency.config file so the file gets processed again.
Would love to hear if that solves the problem!
Thanks Simon, I saw the same issue by coincidence on one of our installations as well. But the odd thing is that I don't see it in my local environment but only on the production environment.
However I will of course try and do what the magnificent Sebastiaan Janssen suggests above :)
/Jan
@Jan I think the problem only appears once <compilation debug="false">, that's when ClientDependencyHandler kicks in and that might trigger it. Anyway, let me know if it helps!
Hi Seb
It's fixed the firefox js error but still showing in chrome - btw my install is currently running in full debug mode
Si
Bizzarely my bodyText field is now showing which was previously not working
Si
@Simon Good to know it also appears in debug mode. Come to think of it, that's not so surprising.
Chrome is notoriously good at a caching stuff a little too agressively, try hard reloading a few times (CTRL+Refresh or SHIFT+Refresh). Also when you have the dev tools open, click on the cog in the lower right corner and enable "Disable cache (while DevTools is open)" if it isn't already on.
Is it the same error?
Alas no - tried clearing out everything from cache as well but still the same error popping through it seems :(
So this error:
Uncaught TypeError: Object [object Object] has no method 'jQuery' UmbracoSpeechBubbleBackend.js:37
UmbracoSpeechBubble.ShowMessage UmbracoSpeechBubbleBackend.js:37
Was obviously caused by the fact that the code says speechBubble.jQuery(".speechClose").show(); insread of jQuery(".speechClose").show();, you would agree with me right? speechBubble has not method jQuery.
So if you fixed that javascript then I don't get why it can give the same error, it should at least be a slightly different error.
One other trick I sometimes use: go to yoursite.local/Umbraco/Js/UmbracoSpeechBubbleBackEnd.js (replace yoursite.local with your own url) and check that line 37 does indeed read: jQuery(".speechClose").show(); without the speechBubble prefix. Hard-refresh it if it doesn't.
Again, this will only work with <compilation debug="true" /> so if that is set to false, make sure to increase the version number in ClientDependency.config.
@Simon could you perhaps try from a different machine? Or perhaps simply just reboot the machine you're currently using. Caching and Chrome can be a bitch sometimes! (I'm first going to try all of the above stuff tomorrow so don't know if it works).
/Jan
Theres some confusion here - my original report was this error:
Unsafe JavaScript attempt to access frame with URL hlngmmdolgbdnnimbmblfhhndibdipaf/images/loader.gif from frame with URL localhost.local/umbraco/umbraco.aspx#content. The frame requesting access has a protocol of 'http', the frame being accessed has a protocol of 'chrome-extension'. Protocols must match. jquery.js:3
Not the speech bubble one - that was only showing in Firefox and is now fixed as I mentioned, however the one posted here is still the rampant rabbit that is causing thousands of errors.
Aha! So: yes, your rich text editors are loading again because the javascript was actually fixed.
And no: there's nothing we can do about a browser plugin throwing errors. I just tried to load the backoffice for 4.7.1 with that plugin installed and it starts throwing the same errors. This is a security measure, possibly enabled in a recent version of Chrome and the only thing you can do about it (as far as I can tell from a quick google search) is disable the security measure in Chrome.
Aha ok cool, as long as I know it's a chrome only issue thats cool - at least we got another bug fixed - cheers dude :-)
is working on a reply...