Closed (fixed)
Project:
Translate Drupal with GTranslate
Version:
7.x-1.9
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Jan 2012 at 14:45 UTC
Updated:
6 Apr 2016 at 15:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
BarisW commentedHere's a D7 version.
Comment #2
ericrdb commentedPatch in #1 worked for me. Thanks
Comment #3
BarisW commentedSlightly improved version by making it protocol independent.
I had some issues with the block being cached in http and then shown in https, introducing insecure content warnings in browsers. By making it protocol independent, this is not an issue anymore.
Like this:
<script type="text/javascript" src="//translate.google.com/translate_a/element.js" />Comment #4
BarisW commentedThe patch is against 7.x-1.x-dev by the way.
Comment #5
pcorbett commentedTested this in 7.x-1.9 and works well for the on-the-fly method. Might make sense to apply the "//" technique to the rest of the hard-coded urls?
Comment #6
gscerb commentedI'm using 7.x-1.10 and Drupal 7.32
On my local developmental site "On the Fly" works well.
On my production HTTPS site. Nothing happens in "On the Fly". But "Redirect" will work.
It seems that the secure HTTPS site causes problems.
Comment #7
joshuautley commentedRunning https which is being forced in settings.php file with no module for secure pages, etc.
Patch #3 with on the fly works for us.
Thank you.
Comment #8
alexgreyhead commented+1 for the patch in 3 - works perfectly :) Thanks :)
Comment #9
larowlan+1 RTBC
Comment #10
seworthi commented+1 RTBC, works great.
Comment #11
cammchugh commentedThe protocol relative approach was included in the 7.11 release. Closing this issue as fixed.