Josh - It still seems that this issue has not yet been fully resolved. After adding the snippet of code supplied by Google to our site, we still get the security message pop up in IE although we have pointed the code to https the page returned still contains no secure content and hence the error in IE.
This issue is currently blocking us from successfully implementing the translator on our site and am keen to have it fixed. Can someone either say when this issue is going to be fully fixed by Google, or how we can workaround it? Thanks On May 13, 12:35 am, Justin Hof wrote: > I had to remove the Google translator for IE when onhttpsas it was > causing too many issues with customers. > (sitehttp://www.deepblueyachtsupply.com) > > Please let me know when this is fully addressed so I can enable it > again. > > Thanks. > > On May 12, 9:20 am, Justin Hof wrote: > > > I have added the code to my site, and have a check to either usehttps > > or http depending on the location. However, in IE (tested using IE 7), > > the security message still pops up, even though the script is loaded > > fromhttpsas noted below. > > > To test yourselves, please go tohttp://www.deepblueyachtsupply.com > > > You'll have to add something to the cart, and go to the checkout > > screen to see the security message. Again, this pops up with IE 7, and > > right now that still represents a good 20% of users based off Google > > Analytics. > > > Let me know if this helps, or if there is a solution in place to fix > > this issue. > > > Thanks, > > Justin > > > On Apr 22, 12:55 am, Josh (Google Employee) wrote: > > > > HI William, > > > > I just tested this. > > > > If you use: > > > > <div id="google_translate_element"></div><script> > > > function googleTranslateElementInit() { > > > new google.translate.TranslateElement({ > > > pageLanguage: 'en' > > > }, 'google_translate_element');} > > > </script><script src="https://translate.google.com/translate_a/ > > > element.js?cb=googleTranslateElementInit"></script> > > > > And the page you put this on is also served fromHTTPS, then all the > > > resources are loaded fromHTTPS. > > > > I wonder if your browsers cache could be causing a problem? If all > > > else fails, try clearing your cache and see if that makes any > > > difference. > > > > Also, if you'd like me to have a look at your page let me know, and > > > I'll look at it specifically. > > > > Best, > > > Josh > > > > On Apr 22, 3:12 am, williamjourdan wrote: > > > > > Hello Josh, > > > > > This does not seem to be fixed, it still loads clear dot image in > > > > http. > > > > Only after choosing other than the default language, I am a bit > > > > desperate to get this working with out the ssl warning. > > > > > Please advise, thanks much! > > > > > On Mar 3, 3:15 pm, Josh (Google Employee) wrote: > > > > > > Hi guys, > > > > > > This has been fixed. > > > > > If you have an SSL website, just point to the SSL version of our > > > > > Element Javascript loader: > > > > > >https://translate.google.com/translate_a/element.js?cb=googleTranslat... > > > > > > Below is the same code that you would copy > > > > > fromhttp://translate.google.com/translate_tools, > > > > > only with the secure loader: > > > > > > <div id="google_translate_element"></div><script> > > > > > function googleTranslateElementInit() { > > > > > new google.translate.TranslateElement({ > > > > > pageLanguage: 'en' > > > > > }, 'google_translate_element');} > > > > > > </script><script src="https://translate.google.com/translate_a/ > > > > > element.js?cb=googleTranslateElementInit"></script> > > > > > > Cheers, > > > > > Josh > > > > > > On Feb 27, 11:44 am, Jack Andolini wrote:> Hi Josh, > > > > > > > When will they release a fix for this? I'm still tryint to make it > > > > > > work in mySSLwebsite. > > > > > > > On Feb 18, 8:15 pm, Josh (Google Employee) wrote: > > > > > > > > Hi Evan, > > > > > > > > Very clever fix. > > > > > > > I've fixed it on our end, but it make take a few days before we > > > > > > > push > > > > > > > the fix live. > > > > > > > > Best, > > > > > > > Josh > > > > > > > > On Feb 18, 4:52 pm, Evan wrote: > > > > > > > > > Oh, and here is a link to the site that I have thehttps:// issue > > > > > > > > "fixed" on... The translate widget is at the bottom right. > > > > > > > > >https://www.southwestmedical.com/ > > > > > > > > > You should get not security warnings or privacy errors, despite > > > > > > > > being > > > > > > > > inhttps://. > > > > > > > > > Like I said before, my solution is very sloppy, and I wouldn't > > > > > > > > recommend others try to duplicate it... This is really an issue > > > > > > > > Google > > > > > > > > should address on their end. > > > > > > > > > Thanks, > > > > > > > > Evan > > > > > > > > > On Feb 18, 3:32 pm, Evan wrote: > > > > > > > > > > If you guys (Google) are really going to fix this to work with > > > > > > > > >SSLout of the box like everyone wants, then don't forget the > > > > > > > > > following: > > > > > > > > > > Line 74 > > > > > > > > > ofhttps://translate.googleapis.com/translate_static/js/element/main.js: > > > > > > > > > > When the JS writes the line to embed the SWF file, the > > > > > > > > > codebase > > > > > > > > > attribute needs to point tohttpsto prevent theIEwarning... so > > > > > > > > > "http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab"; > > > > > > > > > should be > > > > > > > > > "https://download.macromedia.com/pub/shockwave/cabs/flash/ > > > > > > > > > swflash.cab" or have the conditional that checks > > > > > > > > > window.location.protocol. > > > > > > > > > > Then there's the aforementioned issues on line 77 with the two > > > > > > > > > instances ofhttp://www.google.com/images/cleardot.gifthatDavid > > > > > > > > > explained in great detail above... > > > > > > > > > > Then in the > > > > > > > > > file:https://translate.googleapis.com/translate_static/css/translateelemen... > > > > > > > > > you have: > > > > > > > > > .goog-te-balloon-zippy .minus{ > > > > > > > > > background-image:url(http://www.google.com/images/ > > > > > > > > > zippy_minus_sm.gif) > > > > > > > > > > } > > > > > > > > > > .goog-te-balloon-zippy .plus{ > > > > > > > > > background-image:url(http://www.google.com/images/ > > > > > > > > > zippy_plus_sm.gif) > > > > > > > > > > } > > > > > > > > > > So those would need to be changed tohttps:// or made dynamic. > > > > > > > > > > We were able to get the Google Translate Gadget to work on > > > > > > > > > our site > > > > > > > > > withHTTPSand no warning, but I literally had to create this > > > > > > > > > whole > > > > > > > > > elaborate system to sort of "fix" Google's issues on the fly, > > > > > > > > > and then > > > > > > > > > also proxy through certain files so they loaded from our > > > > > > > > > domain > > > > > > > > > because the googleapis.com domain was sometimes trying to set > > > > > > > > > cookies > > > > > > > > > while embedded on our domain, which causes that nasty looking > > > > > > > > > eye with > > > > > > > > > a red warning icon at the bottom ofIE, at least in IE7+ with > > > > > > > > > default > > > > > > > > > settings. It's an ugly fix, but with so many international > > > > > > > > > customers, this tool is too valuable for us not to have, and > > > > > > > > > those > > > > > > > > > security warnings KILL conversion rates like none other. > > > > > > > > > > Now if only they'd make it rewrite form actions to have the > > > > > > > > > hash tag > > > > > > > > > in the URL to keep the translation on the next page when a > > > > > > > > > form is > > > > > > > > > submitted.... Right now it seems they're only rewriting the > > > > > > > > > href > > > > > > > > > attribute of <a> tags. I bet it would take 10 seconds to fix > > > > > > > > > that > > > > > > > > > myself with some quick jQuery magic though. > > > > > > > > > > Anyway, hope this helps Google and maybe some of the other > > > > > > > > > people who > > > > > > > > > are struggling with that horriblehttpsissue. > > > > > > > > > > Evan > > > > > > > > > > On Feb 16, 4:10 pm, Josh (Google Employee) wrote: > > > > > > > > > > > Hi David, > > > > > > > > > > > Thanks so much for the detailed bug report, and helping us > > > > > > > > > > find our > > > > > > > > > > bug! > > > > > > > > > > We'll get that fixed as soon as we can. > > > > > > > > > > > Best, > > > > > > > > > > Josh > > > > > > > > > > > On Feb 13, 4:50 am, David Gouldby wrote: > > > > > > > > > > > > I believe I've reverse-engineered the source of the bug, > > > > > > > > > > > I'm copying > > > > > > > > > > > another post that I made elsewhere regarding this: > > > > > > > > > > > > We've had the translator implemented on a secure control > > > > > > > > > > > panel for a > > > > > > > > > > > few weeks now, it has been working fine. > > > > > > > > > > > But today, it started to throw warnings, stating that > > > > > > > > > > > some of the > > > > > > > > > > > content was not loaded securely. > > > > > > > > > > > > Firstly, looking at the page source code, I found the > > > > > > > > > > > content that > > > > > > > > > > > wasn't loaded throughHTTPS, the link > > > > > > > > > > > is:http://www.google.com/images/cleardot.gif > > > > > > > > > > > > This image URL isn't specified in our code, so I tried > > > > > > > > > > > going backwards > > > > > > > > > > > through the Google code/scripts, and I ended up > > > > > > > > > > > here:https://translate.googleapis.com/translate_static/js/element/main.js > > > > > > > > > > > > I found 2 references to cleardot.gif in this javascript: > > > > > > > > > > > > Line 10: > > > > > > > > > > > protocol=="https:"?"https://":"http://",rc=qc+"www.google.com/ > > > > > > > > > > > images/cleardot.gif" > > > > > > > > > > > As you can see here, the code chooses between http > > > > > > > > > > > orhttps, so that > > > > > > > > > > > works fine. > > > > > > > > > > > > However, on line 77, there is no such code to swap > > > > > > > > > > > between http and > > > > > > > > > > >https: > > > > > > > > > > > > a.Xa+"',sizingMethod='scale');\"></span>":'<img > > > > > > > > > > > src="'+a.Xa+'">','</ > > > > > > > > > > > td><td width=8></td><td width=1 nowrap><a id="close" > > > > > > > > > > > href="javascript:void(0)" title="',"Close",'"><img > > > > > > > > > > > src="http://www.google.com/images/cleardot.gif"; > > > > > > > > > > > width="15" height="15" > > > > > > > > > > > style="background-image:url(',a.Qc,');background-position:-28px > > > > > > > > > > > 0px"></ > > > > > > > > > > > a></td></tr></table><div id="original" > > > > > > > > > > > class="goog-te-balloon-text"></ > > > > > > > > > > > div><div id="zippy" class="goog-te-balloon-zippy" > > > > > > > > > > > style="display:none"><img id="zippy_img" class="plus" > > > > > > > > > > > width="12" > > > > > > > > > > > height="12" > > > > > > > > > > > src="http://www.google.com/images/cleardot.gif";><span>', > > > > > > > > > > > > It loads this image through HTTP only, this is what is > > > > > > > > > > > throwing these > > > > > > > > > > > warning messages for us. > > > > > > > > > > > > Can the same http/httpscode be added to line 77 from line > > > > > > > > > > > 10? > > > > > > > > > > > > On Feb 3, 8:55 pm, Chris Green wrote: > > > > > > > > > > > > > Try this thenhttps://trade.absentfriends.com/home.aspx > > ... > > read more » -- You received this message because you are subscribed to the Google Groups "General" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-translate-general?hl=en.
![http://www.google.com/images/cleardot.gif"](https://www.google.com/images/cleardot.gif"){kind=link}