Jump to:
| Project: | Internationalization |
| Version: | 7.x-1.0 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
First, it may simply be that I mis-understand what that module does, but I currently have my site translated into multiple languages (English, Chinese, Danish, Italian) ... when I set my Safari to Danish, as an example, and go to http://www.google.com, everything comes up Danish ... when I go to my web page (http://www.hub.org), everything comes up English ...
Shouldn't enabling that module result in it redirecting to the Danish version automatically, or am I misunderstanding ... ?
In case its simple a mis-configuration of settings,the only place I could think of was under:
Configuration -> Regional and language ->Detection and Selection
Where I have URL, User, Browser and Default all checked ...
Help appreciated to get this to work ... thx ...
Comments
#1
The module just redirects web crawlers (anonymous users) when there's a mismatch between the content language and the language prefix, or url.
Nothing to do with browser languages and front page.
#2
I just confirmed that the intended use case doesn't work either, at least with language domains.
I've got the following pages:
When I'm logged out and surf to http://fr.site.example.com/node/1, I should get redirected to http://en.site.example.com/node/1, but I don't. Instead, I'm left on that page with a French interface and English content.
When I'm logged out and surf to http://en.site.example.com/node/2, I should get redirected to http://fr.site.example.com/node/2, but I don't. Instead, I'm left on that page with an English interface and French content.
I even tried checking all of the above checkboxes, submitting and then clearing the cache, but that didn't help either.
#3
Same here.
#4
More accurate title
#5
Actually it didn't work for me with prefixes either.
#6
Do you have them prioritized properly, the user browser/language at the top?
#7
Actually you need to set URL at the top.
Please check you have that setting right.
#8
For those of you having this issue, do you have the Multilingual content module enabled? Translation redirect actually doesn't figure out the page to redirect on its own. It relies on another module to figure it out. The Multilingual content module does this for node pages.
I just updated the Translation redirect module documentation because this was definitely *not* clear. Perhaps there should be a README.txt file added to the module directory as well.
Another note is that the Global Redirect module has i18n issues. If you are using that module, you should use the latest *dev* version of the module rather than version 1.4.
Kristen
#9
Right. Thanks Kristen.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.