pozzad

Hi
fixed on 1.2.4

Hi I’ve tested the following urls:
https://www.ashkarmusicanddance.com/it/
https://www.ronitbaras.com/it/
and both of them correctly return a translated page with a 200 status code.
The 503 should be returned only when trying to access a not yet translated page.

Global translator uses the DB only for saving the configuration options:
the cached files are saved on the filesystem.
On my blog I have more that 50000 translated pages without any memory problem…

Hi there could be a lot of causes related to the message “Bad or unhandled response…” Did you upgraded to the latest version? If you switch to another language you shouldn’t loose the already translated pages

You’re the first user submitting this kind of issue… The plugin doesn’t require a lot of memory to work. Perharps you have a conflicting plugin or a strange PHP configuration…

Hi
the first issue sounds very strange, anyway I’ll try to reproduce it.
the second one is due to some changes on Gogle API and should be solved by installing the 1.2.3, but it will not fix the already translated pages.

Hi
the 503 error (which means “temporarily unavailable”) is correct and it is returned if you try to translate more that one page with a delay < 5 minutes. This is needed in order to prevent banning from Google.

Hi all!
Google has just changed its translation URL, so all the old versions cannot work anymore!!
I’ve just released a fix: please download the 1.2.2 version ??

Davide Pozza

Hi all!
Google has just changed its translation URL, so all the old versions cannot work anymore!!
I’ve just released a fix: please download the 1.2.2 version ??

Davide Pozza

Hi 0xCAFE, this should mean that you’ve upgraded from 1.0.8.1. All the previous versions used a cache dir inside the plugin dir. Starting from 1.0.8.1 the cache dir has been moved inside wp-content dir in order to support the automatic update (which works by fully deleting the previous plugin dir and uploading the new one)

Davide

Hi
The 1.0.8.1 will automatically move the old cached files (inside global-translator/cache) to the new cache location (gt-cache).

The message “deleting BAD cached version” should no matter with the cache moving issue.

You have just to manually upgrade to 1.0.8.1 (by overriding the previous version).

Davide

Hi
Fixed on 1.0.7
If you’re using this version and it is not working please let me know (but make sure to test a page translated by this version ?? )
Davide

This seems to be a translation engine issue. It doesn’t seem to depend on GT

Davide

Starting from 1.0 version a new control has been added in order to solve this problem: when you remove a translation all the corresponding url will return a 404 Not found.

Davide

Hi all
The version 1.0 (just released) should drammatically reduce the ban risk.
I suggest you to download and install it asap.

Davide