[Plugin: Global Translator]: Bad or unhandled response from GOOGLE

Resolved xirb
(@xirb)

15 years, 6 months ago

I have installed the Global Translator plugin on my site http://www.eeepc.dk/ but it doen’t work.

I have not seen a single translated page yet..
What hapens is that the would-be translated pages just forwards to the main page.. E.g.: http://www.eeepc.dk/en/ goes directly to the above URL without the /en/ (please try for yourself).. The single posts acts the same way.

I get these messages from the plugin page:

Your cache directory currently contains 111 successfully translated and cached pages. Cache directory size: 2.5 MB

– But apparently I cannot access any of these pages.

Your stale directory currently contains 0 successfully translated and cached pages waiting for a new translation.
Stale directory size: 0 MB

I also get this message:
Translations status: Bad or unhandled response from the ‘GOOGLE’ translation engine.

Do anybody have any idea what could be wrong? Is there any other plugins that stops this translation plugin form working?

THANK YOU VERY MUCH for any help!
Best regards

http://wordpress.org/extend/plugins/global-translator/

Viewing 9 replies - 1 through 9 (of 9 total)

Thread Starter xirb
(@xirb)

15 years, 6 months ago

I found the problems and solutions.
I actualle had 2 unrelated problems:

1) The error message from Google: “Translations status: Bad or unhandled response from the ‘GOOGLE’ translation engine. “
Don’t know if this was just a temporary error from Google, but I tweaked the settings a bit to make them less aggressive with more than 600 seconds between requests. Now Google didn’t complain. But I still could not access the translated pages.. :

2)
E.g. entering the German version of Eee PC blog with /de/ it just redirected to the frontpage in the blogs native language. I found that this was caused by a plugin I have installed called Permanlink Redirect. This makes sure that things can only be accessed in one way but also messes with the links needed to access the language pages. The solution was easy: Just go to the Permanlink Redirect settings page and add the paths to be skipped.. E.g. /ru/ for Russian as in the last part of Eee PC Blog in Russian , /es/ for Spanish Eee Blog in Spanish and /fr/ for French Eee PC Blog in Frenchand so on –
I think you get the picture on hat to add. 😉

kreestal
(@kreestal)

15 years, 6 months ago

I keep having that exact problem, even one week after I installed the plugin… 🙁

xirb, how much time did it tale to work?

jayen
(@jayen)

15 years, 6 months ago

HI xirb

I also have the Permanlink Redirect plugin installed (Latest Version) But i’m not having any problems with it at all. I didn’t have to change any of it’s settings 🙂

I also had to extend the time between translations, I do still get the occasional warning from google but it’s working most of the time 🙂 Once it has the whole blog translated i don’t suppose we’ll have these problems again, unless of cause we’re publishing a lot of content like every 5 mins 🙂

Jayen

flapane
(@flapane)

15 years, 1 month ago

“Bad or unhandled response from the ‘GOOGLE’ translation engine” here with 600sec of delay between translations.
It was working well using this interval ’till some days ago.

flapane
(@flapane)

15 years, 1 month ago

I think that there should be a “magic” delay, as I have put 3600sec and still nothing changes.

flapane
(@flapane)

15 years, 1 month ago

20000 sec and still the debug log says: We believe that this is an automatic translation it has been blocked blah blah and blah.

tankg
(@tankg)

15 years ago

You’d better check the debug box, and then go through the debug.log file, cos’ it might bee something else than a ban from google…

flapane
(@flapane)

15 years ago

Hi tankg,
first thing I did, it says that Google thinks that it is an automatic translation blah blah and blah. It happend after I deactivated it for 3 days after having tried some days with delay at 99000 secs.
Now I activated it another time last night after some days, it still says BAD OR UNHANDLED [….] and the log says (the text pasted above is repeated in the whole log, the post addresses are the only thing that change):
Complete log at http://www.flapane.com/blog/wp-content/plugins/global-translator/debug.log

2009-04-02 08:23:37 [from: 38.99.13.123|Mozilla/5.0] – gltr_get_page_content :: Connecting to engine for url:http://www.flapane.com/blog/tag/update-firmware/
2009-04-02 08:23:37 [from: 38.99.13.123|Mozilla/5.0] – gltr_clean_url_to_translate :: [REWRITEON] self url:http://www.flapane.com/blog/de/tag/update-firmware/ | url_to_translate:http://www.flapane.com/blog/tag/update-firmware/
2009-04-02 08:23:37 [from: 38.99.13.123|Mozilla/5.0] – gltr_is_connection_allowed :: Blocking connection request: delta=214 secs
2009-04-02 08:23:37 [from: 38.99.13.123|Mozilla/5.0] – gltr_get_page_content :: translation not available. Switching to stale for url: http://www.flapane.com/blog/tag/update-firmware/
2009-04-02 08:23:37 [from: 38.99.13.123|Mozilla/5.0] – gltr_get_page_content :: returning stale version (_blog_de_tag_update-firmware) for url:http://www.flapane.com/blog/tag/update-firmware/
2009-04-02 08:30:20 [from: 66.249.65.193|Mozilla/5.0] – gltr_clean_url_to_translate :: [REWRITEON] self url:http://www.flapane.com/blog/es/tag/apache/ | url_to_translate:http://www.flapane.com/blog/tag/apache/
2009-04-02 08:30:20 [from: 66.249.65.193|Mozilla/5.0] – gltr_get_page_content :: Connecting to engine for url:http://www.flapane.com/blog/tag/apache/
2009-04-02 08:30:20 [from: 66.249.65.193|Mozilla/5.0] – gltr_clean_url_to_translate :: [REWRITEON] self url:http://www.flapane.com/blog/es/tag/apache/ | url_to_translate:http://www.flapane.com/blog/tag/apache/
2009-04-02 08:30:20 [from: 66.249.65.193|Mozilla/5.0] – gltr_is_connection_allowed :: Allowing connection request: delta=617 secs
2009-04-02 08:30:20 [from: 66.249.65.193|Mozilla/5.0] – gltr_patch_translation_url :: Google Patched:
2009-04-02 08:30:20 [from: 66.249.65.193|Mozilla/5.0] – Bad translated content for url: http://www.flapane.com/blog/tag/apache/
php_network_getaddresses: getaddrinfo failed: Name or service not known (0)

2009-04-02 08:30:20 [from: 66.249.65.193|Mozilla/5.0] – gltr_get_page_content :: translation not available. Switching to stale for url: http://www.flapane.com/blog/tag/apache/
2009-04-02 08:30:20 [from: 66.249.65.193|Mozilla/5.0] – gltr_get_page_content :: returning stale version (_blog_es_tag_apache) for url:http://www.flapane.com/blog/tag/apache/
2009-04-02 08:36:08 [from: 75.22.28.38|Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032710 Ubuntu/8.04] – gltr_clean_url_to_translate :: [REWRITEON] self url:http://www.flapane.com/blog/en/2009/03/sourceslist-per-repository-di-ubuntu-hardy-804-aggiornata-al-5-marzo-2009/ | url_to_translate:http://www.flapane.com/blog/2009/03/sourceslist-per-repository-di-ubuntu-hardy-804-aggiornata-al-5-marzo-2009/
2009-04-02 08:36:08 [from: 75.22.28.38|Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032710 Ubuntu/8.04] – gltr_get_page_content :: Connecting to engine for url:http://www.flapane.com/blog/2009/03/sourceslist-per-repository-di-ubuntu-hardy-804-aggiornata-al-5-marzo-2009/
2009-04-02 08:36:08 [from: 75.22.28.38|Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032710 Ubuntu/8.04] – gltr_clean_url_to_translate :: [REWRITEON] self url:http://www.flapane.com/blog/en/2009/03/sourceslist-per-repository-di-ubuntu-hardy-804-aggiornata-al-5-marzo-2009/ | url_to_translate:http://www.flapane.com/blog/2009/03/sourceslist-per-repository-di-ubuntu-hardy-804-aggiornata-al-5-marzo-2009/
2009-04-02 08:36:08 [from: 75.22.28.38|Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032710 Ubuntu/8.04] – gltr_is_connection_allowed :: Blocking connection request: delta=348 secs
2009-04-02 08:36:08 [from: 75.22.28.38|Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032710 Ubuntu/8.04] – gltr_get_page_content :: translation not available. Switching to stale for url: http://www.flapane.com/blog/2009/03/sourceslist-per-repository-di-ubuntu-hardy-804-aggiornata-al-5-marzo-2009/
2009-04-02 08:36:08 [from: 75.22.28.38|Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032710 Ubuntu/8.04] – gltr_get_page_content :: returning stale version (_blog_en_2009_03_sourceslist-per-repository-di-ubuntu-hardy-804-aggiornata-al-5-marzo-2009) for url:http://www.flapane.com/blog/2009/03/sourceslist-per-repository-di-ubuntu-hardy-804-aggiornata-al-5-marzo-2009/

tankg
(@tankg)

15 years ago

Hi Flapane, maybe you checked the other threads, hence you got the answer (i.e download the 1.2.2.1 version) since google changed it’s code…
Best Regards.