Clicking any flag will take us to GT but the block is still visible. I believe this is a wrong behavior and it should be disabled not to create a 'nested translation'.

I have the block set as Content Top.

Comments

vako’s picture

vako commented

you can check the behavior at : www.keghart.com

vako’s picture

vako commented
Version: 6.x-1.x-dev » 6.x-2.0-beta1
blinkingtwelve’s picture

blinkingtwelve commented
Assigned: Unassigned » blinkingtwelve

It may well be the case that some http load balancer or reverse proxy or something in your webserver setup is stripping out the HTTP 'VIA' header. This module uses the fact that Google sets this header to 'translate.google.com' to determine that a certain request is coming from the GT's translating proxies. Ask your hoster.
A simple testcase would be to upload a php script like this one:

print($_SERVER["HTTP_VIA"]);

make it publicly accessible (check it) and feed it into Google Translate. The output should contain 'translate.google.com'.

vako’s picture

vako commented

your code is coming back with: 1,0 TWSFE/0.9 translate.google.com
it does contain the text you were expecting.

How can I describe this situation to my host or what should I ask them?

blinkingtwelve’s picture

blinkingtwelve commented

So the header is getting through.
Another thought. Do you have caching enabled in Drupal?

vako’s picture

vako commented

Yes, I do, I also have the Boost module. I disabled both and cleared their cache. Still having the same issue.

I noticed another issue popping-up (even before I disabled the cache); sometimes, when I click on any of the flags, I get the following message:

We are not yet able to translate from Armenian into French.

even though we are not translating anything from Armenian!!
Try it please.

vako’s picture

vako commented

Also I have received several complaints from viewers that the pages are not translating what they want, so I am only displaying the block on the front page now. the nodes don't have it.

blinkingtwelve’s picture

blinkingtwelve commented
Status: Active » Postponed (maintainer needs more info)

I'm out of ideas on your sites' problem. Setting this to 'postponed' until related bug reports from other sites come in - maybe then we'll find a common cause.

vako’s picture

vako commented

under /admin/settings/language I had Armenian as the 1st option, although English was the default selected. I deleted Armenian and the site worked for couple of hours, until I started messing around with the flags (added couple) then the problem came back!
Do you think GT was picking-up the 1st option from Drupal?

I change the location of the Block from content top to Left sidelink without any improvement as well.

so far I have the following three issues, hopefully we can find a solution in the future:
- After the translation, we land on a different page.
- Block still visible after the translation (in GT)
- Sometimes, the page cannot be translated and picks-up the wrong language code.

torvall’s picture

torvall commented

Hello,

I posted a new issue (#831238: Google Translate Links module incompatible with aggressive cache mode) that may be a duplicate of this one. As I stated at that post, if you have aggressive mode caching enabled, the block will be displayed on translated pages.

This is an old thread and the issue may be no longer valid but I decided to post this anyway, just for the record.

blinkingtwelve’s picture

blinkingtwelve commented

Vako, we discussed caching earlier on but it might be worthwile to check with current CVS to see if it solves the problem.

blinkingtwelve’s picture

blinkingtwelve commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

No CVS testing report from Vako but my guess is that it was a problem with aggressive caching, which should be fixed in 2.1.