Google Translate no longer working | LWT: Basic questions, set up, troubleshooting, feedback | Forum
Log In
Register
Home
Topic RSS
Related Topics
04:28
July 5, 2011
Offline
A few days ago, Google Translate (both put in as Dict1 and as GTranslate) stopped working in both my local and FI3M version of Learning with Texts. I assume this is because of a change in the way that Google Translate is handling post variables or something like that; anyone have any insight on how I can get it back up?
04:53
moderator
June 25, 2011
Offline
I take the liberty of quoting from the developer's forum:
2012-02-13 12:48:25 PST
Please put an asterisk "*" in front of the Google Translate URI in your language setting(s), e.g. for French *http://translate.google.de/?ie=UTF-8'sl=fr'tl=en'text=### Then a new popup window will open (check any popup blocker if not). Google Translate seems to work then. If you keep the new window open all the time, the position and size of the popup window will be remembered and not changed.
[...]
I hope this workaround helps. And maybe google'll reenable this feature soon (it seems like they changed their policy twice in the last couple of days).
Focusing on:
Next target: 
Abandoned: 
00:24
August 3, 2011
Offline
The above described problem doesn't anymore exist. Google Translate displays its results in a frame without problems. If this problem occurs again in the future, please follow the following advice:
Please put an asterisk "*" in front of the Google Translate URI in your language setting(s), e.g. for French *http://translate.google.de/?ie=UTF-8'sl=fr'tl=en'text=### Then a new popup window will open (check any popup blocker if not). Google Translate seems to work then. If you keep the new window open all the time, the position and size of the popup window will be remembered and not changed.
00:11
November 23, 2011
Offline
I followed the solution outlined above; inserted a star "*" before both of the URI for the dictionary and google in the language setting on LWT. However this did not resolve the issue. Any thoughts?
15:36
moderator
June 25, 2011
Offline
rcrichards said:
I followed the solution outlined above; inserted a star "*" before both of the URI for the dictionary and google in the language setting on LWT. However this did not resolve the issue. Any thoughts?
I tried to reproduce the error, but the asterisk seems to work as designed: if I click on "GTr", a new window containing the result of the lookup pops up. If you provide us with more details (and maybe screenshots) regarding your an exact description of the problem (do you see a popup window? If so, can you provide a screenshot?), your LWT settings, OS and Browser (popup blockers active?) etc, maybe someone can come up with a workaround.
Focusing on:
Next target:
Abandoned:
17:07
November 23, 2011
Offline
Lingo,
I am using safari in windows 7 with default LWT settings, but the problem appears to be that pop-ups are blocked in the browser as a default (or were). Google is officially off my Christmas card list for this stunt.
Rob
23:54
July 5, 2011
Offline
Command+Shift+K should toggle pop-up blocking on and off in Safari.
13:52
moderator
June 25, 2011
Offline
This post does not offer a solution to the problem and if you do not consider yourself an computer geek, this post is probably not worth reading. Hopefully, this post can motivate some people to look further for other workarounds or start their own research/development…
If you look at the response (for instance, using http://web-sniffer.net/ ) to a typical Google translate URI, you'll notice "X-Frame-Options:SAMEORIGIN" (see here for an explanation; I suppose this might be related).
I wonder if the following quote can lead to something:
Quote from vtimashkov.wordpress.com
So I needed somehow to ask the browser to ignore this response header. Unfortunately Firefox doesn’t have any option for it. So I had either to use some intermediary proxy like WebScarab, or to use Fiddler 2 asking it to remove undesired header.
I used the last one. There is documentation how to remove header from response stream in Fiddler 2. It worked like a charm.
I did not take the time to determine whether google uses (on top of this) a js-based Framekiller (see the wikipedia link for proposition on how to override framekillers; I believe – without ever having tested it – that the greasemonkey addon for Firefox could also be useful in this context).
Focusing on:
Next target:
Abandoned:
Most Users Ever Online: 522
Currently Online:
12 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Kevinpost: 498
Randybvain: 450
this_just_in: 328
Alasdair: 304
sipes23: 260
NKellyEmerald: 231
Member Stats:
Guest Posters: 7
Members: 19257
Moderators: 2
Admins: 1
Forum Stats:
Groups: 5
Forums: 16
Topics: 2660
Posts: 15226
Newest Members: shenagaxop, pashli, VioletPurpura180, tuknuzdm, Sanny006, Phillip
Moderators: Lingo (268), anno (205)
Administrators: Benny (459)
Comments on this entry are closed.