I am trying to build multilanguage site using v.6.2. But I got unknown issue, I am not sure that it's bug or not...

1. Enabled Locale + Content translation module
2. Added new language (XXX), Default is YYY.
3. Edited content type (both story & pagy) to support translations.
4. Created new story in YYY language
5. Created translation of content in XXX language of above content.
6. Language config : Path prefix with language fallback.

Current site language was YYY,
The above content shows in XXX language.
I switched site language to XXX.
The above content still shows in XXX language.
I switched site language to YYY.
The above content still shows in XXX language.
-------------------------------------------

I wanted this to work like :

When current site language is XXX, then it should show content in XXX language. When switches site language to YYY, then it should show content in YYY language FIRSTLY.

Am I doing something wrong? or its' known issue?

Comments

gobioasis’s picture

gobioasis commented
Priority: Normal » Critical

any one?

Language switcher is useless or ... ?

jlscheidegger’s picture

jlscheidegger commented

I have the same issue and no "Translate" tab to translate menus or content.

strellman’s picture

strellman commented

It has been a month. Can you clarify? Are you using i18n for translation of menus, etc.? Did you extract the language tarbal for drupal6 in your root directory before adding the language? If not, I suggest you delete the language and add it again if you want drupal itself translated. Have you tried another Language config besides Path prefix with language fallback to test?

Alan Oliveira’s picture

Alan Oliveira commented

i got the same problem

current, Im building a drupal website in 3 languages:
* portuguese /?q=/
* english /?q=us/
* spanish /?q=es/

the entire portuguese site is almost ready, when i begin translate content to other languages I've noticed that drupal "create" another node example:

product page in portuguese is current node/1
its translated version to english is node/132
and to spanish is node/133

when i click on Language switcher, simulating an anonymous navigation, the node remain in portuguese, and i gotta click on english to see the translation, ... even with the /?q=us/node/1 on the adrress bar, the node dont turn to english automaticaly, so i gotta keep switching languages each time i navigate =(

are there a way to let the Language switcher, in fact, control the node translated content ?

aniruddhamallik’s picture

aniruddhamallik commented
Version: 6.2 » 6.4

Same here... I have enabled everything required and have also put the translated content in place, but no matter what language I switch to, the site stays in the English mode. Weird...

strellman’s picture

strellman commented
Title: switch language » language domain protocol syntax unclear
Version: 6.4 » 6.6
Assigned: gobioasis » Unassigned

I believe Shuvuu's problem is in using the domain to determine language. If you don't prefix the domain with http:// in the configuration (admin/settings/language/edit/XX) then nothing happens when you switch languages.

There is another problem here too. The help text needs to clarify what is meant by a "protocol".

This value must include a protocol as part of the string. Example: Specifying "http://example.de" or "http://de.example.com" as language domains for German results in URLs in the forms "http://example.de/node" and "http://de.example.com/node", respectively.

This is the behavior I see. My links to "node/31" become doubled to "http://de.example.com/node/node/31". Does this mean I should just drop "node/" in my links and make them "31" or is this going to cause more problems in the future? Inserting "node" makes URL paths unusable.

strellman’s picture

strellman commented
Category: support » bug

I found a work around. If you precede your internal links with a / (for example /node/31) it doesn't add a 2nd "node" in the URL. Still sounds like a bug though.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Category: bug » support
Priority: Critical » Normal
Status: Active » Closed (works as designed)

There seem to be multiple reports tacked into this issue. The original problem echoed in multiple comments is that site language switching does not switch node languages. This is how it works. Different node translations of the same content has different urls, so just changing language without changing node URL does not change the language of the content being shown, just the interface. It is up to contributed modules to implement different language switching and listing schemes for content (there is not one single solution to use).

dps: your browser handles relative links on pages such as node/13 to node/17 as if you are going relatively from node/13, so it goes to node/node/17. It is a browser behavior not a Drupal behavior. This would however be a different bug report / support request.