We've recently started using the Google +1 button on our page, but whenever we include the Google script block this JavaScript error comes up in IE8:
"No relay set (used as
window.postMessage targetOrigin),
cannot send cross-domain message"
This is a weird one, can't find out much about it. Does anyone have any clue what it means? I've tried moving the script include to the top of the page, but it doesn't help.
Google +1 currently does not work on any version of IE.
Related
I am trying to setup GA4 pageviews by configurating on Google Tag Manager. I've done this multiple times for multiple websites and I've never come across this problem before. I am not a technical expert, but I do have some technical knowledge. I just don't understand what exactly is going wrong..
So, the problem...
Basically I have a clean, fresh made container and the GTM codes are properly implemented according to Google Guidelines. The head code is placed at the start of the head opening tag and the body code is placed directly after the body opening tag.
For some reason my container just isn't loading. These are all datalayers that are being pushed:
My pageview requires event = gtm.js which is being pushed on "Container loaded"..
So the first problem is that the "container loaded" does not appear. I have no idea why, but what I found out is when I try to look in dev. console on the GTM debug page, i get a 403 error:
Note, this dev console error does not show in the regular non-test version, only in debug mode. On the website all JS files are status 200.
I am stuck with this one and I just can't seem to figure it out. If someone can give any leads or advise on how to proceed it will be greatly appreciated. Feel free to ask additional information. Thanks in advance!
I just introduced tinyMCE into my rails 4.2.8 site to let manage formatted text in articles. Everything works fine actually but now and then a warning message produced by tinyMCE comes up such as "failed to load content css: http://myurl/assets/tinymce/skins/lightgray/content.min.css" but if a look at the debug console in firefox I see that url has perfectly found and loaded content.min.css.
When the warning message is there I can't enter anything in the textarea but the situation is fixed by reloading the page, then the rich text can be nicely entered and the relevant data is loaded correctly into the backend DB via relevant input form.
I don't understand the reason why tinyMCE is signalling such a warning despite the fact that the css file was actually found.
Any idea? Thanks and kind regards
Vincenzo
**** update on June 8th 2017 ****
Now I can better explain what's actually going on.
1) the problem shows up in Firefox v.53, if I use Chrome everything works fine
2) I am using tinyMCE in three distinct forms: one for new articles, one for editing, one for comments.
3) If I insert a few new articles no problem appears, the problem shows up just chenging the form in use: i.e. after insertion an article I try editing it or another one or else I try to insert a comment after havine inserted a new article. After the error message has shown I can always recover by reloading the page and no error appears eventually.
I guess there is some caching problem specifically in Firefox since all works fine in Chrome. I will try Windows Edge too..
2017/06/10
Tried Windows Edge on Win10: it works fine too.
2017/06/14
In the meantime I opened bug 1371910 at https://bugzilla.mozilla.org/show_bug.cgi?id=1371910#c5 a few days ago and the result was:
QUOTE
Hi Vincenzo,
Thanks for sending us the link. Unfortunately this seems to be a problem with tinyMCE rather than Firefox.
The initial load of content.min.css works correctly, and no other attempts to reload it seem to be made.
If it works in other browsers it is probably due to the developers doing things differently.
If you still think this is a bug in Firefox, please reopen this bug, and send us a smaller test case.
PS. Others seem to be having the same problem as you: https://community.tinymce.com/communityQuestion?id=90661000000Qct9AAC
I hope you find a way to fix it.
UNQUOTE
What the Firefox support says makes sense since I too whatched the content.min.css file was actually loaded by the browser so in must be tinyMCE to misinterpret something. Anyway I am still in the soup...
Whoever might have some interest at this issue please hava a look at:
http://vinloren-learn-rails.herokuapp.com/articles accessing this endpoint with Firefox v52..v54 the click show any article then going back via the 'back' link at the end of the article's content.
I have created an app script using user account 1 and used the script on a Google site. When I view the site using user account 2 , I receive a warning message which can be dismissed.
I have made a copy of the same script on the same site, however there is no option to dismiss this script. I would like to know what would cause this problem as the new script is an exact copy of the old script.
Copy Script http://i.stack.imgur.com/R151l.jpg
Original Script http://i.stack.imgur.com/FIyhm.jpg
If you mean the warning DOES NOT APPEAR then it doesn't show up if you're logged in as the owner of this script (app).
If you made the copy from account2 and are viewing it from the same then you won't see it.
I have installed Chrome on iPhone 4 and script 1 does not work when I use the following lines to call my html page, however the same script works with Chrome installed on Android and PC.
Script1:
output.setSandboxMode(HtmlService.SandboxMode.NATIVE);
However, when I use the following code, it works.
Script 2:
output.setSandboxMode(HtmlService.SandboxMode.IFRAME);
Now, the problem with script 1 is that I get a warning which is dismissable (This application is created by another user.), with script 2 I cannot dismiss the warning. That is why I want to use script 1 universally.
Will someone help me know how can I make script 1 work on Chrome for iOS?
We use the standard Google Website Translator gadget on our site http://ut.no.
The "Contribute a better translation" feature has stopped working. When you click on the "Contribute" button, you get this javascript error:
TypeError: undefined is not an object (evaluating 'a[hd][H]')
in "element_main.js" injected by Google.
This worked fine several weeks ago. Are anyone else having this problem, or is it only us?
After some testing, I fond out that it's the meta tag from Google that's part of the problem.
Removing the "google-translate-customization" meta tag makes the suggestions work, but the suggestion never gets delivered to our Website Translator page.
I installed a WP theme recently and am having trouble getting a Facebook conversion box to display when I visit my site through Chrome. This problem doesn't exist on Firefox.
The response I get on Chrome is no visible pop-up box, but upon inspecting the element, I do see the code for the box in my header.php with a line from the Chrome User Agent saying:
script {
display: none;
Is there a CSS solution to override the User Agent and get the script to display? Again, I have no problems with the theme on Firefox. Here's a link to my site.
Thanks in advance!
I think I found the source of your problem. It's a browser extension.
Your conversion box appears on my personal laptop. However, it doesn't on my work laptop. That lead me to believe that it was a conflict with the script & a browser extension. So I opened your site in an incognito window. Voila! it worked. The next step was figuring out which extension was blocking it. For me, it is LastPass (my work requires the use of LastPass).
If you have LastPass enabled as an extension, disable it. Then test again.
It'd also be a good idea to get these console errors figured out:
Uncaught SyntaxError: Unexpected token ; (index):476
carouFredSel: No element found for "#foo1". jquery.carouFredSel-6.2.1.js?ver=3.8.3:4232
Uncaught ReferenceError: paginateVal is not defined cgview.js?ver=3.8.3:28
Solutions
Unfortunately, there isn't much you can do about people's individual extensions. If this is an absolutely critical feature for you, I'd look at finding a different implementation of it. One that does not conflict with common extensions (that's the easy option).
The other option (harder) is to look into the code of the plugin/script that you're using for the conversion box and identify the conflict.
Last option (hardest) is to look at LastPass extension source code and identify the bug that is preventing other scripts from running. I've had issues with LastPass interfering with javascript in the past.