Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.After using the google translate module successfully for several days, it suddenly stopped working. The problem appears to be related to a change in the IP address of the translate service.
The last release includes the google translate url as: translate.google.com
The cvs head includes the url as an IP: 64.233.179.104
Both of these occasionally issue a 302 redirect to: 209.85.135.104 (2/29/2008 and 3/1/2008)
Currently, the google translate module does not follow the redirection. When faced with a 302, it fails the strlen($content) > 30 test and the page is displayed in the default language. This may be the source of many of the issues currently open for the module.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | gtrans.module.txt | 7.25 KB | drutube |
| redirectionHandling.patch | 5.77 KB | Brett Haranin |
Comments
Comment #1
Brett Haranin commentedComment #2
Brett Haranin commentedComment #3
drutube commentedWhen I applied this patch again 5.x-1.4 I got
Hunk #1 succeeded at 126 (offset -2 lines).
Hunk #2 FAILED at 202
When it is applied to 5.x-1.3 it worked. This patch makes the module work -- sort of. Before applying the patch the module didn't do anything. There have been numerous similar bug reports. While the module still needs much work this patch is a good first step.
I'm attaching the patched module here. Remember the patch is again 5.x-13 not the current release.
Comment #4
avpadernoI am closing this issue, since Drupal 5 and Drupal 6 are now not supported.