Drupal: 7.19
ET: 7.x-1.x-dev (first, than downgraded to 7.x-1.0-beta2)
Pathauto: 7.x-1.2
Detection and selection (both user interface and content): Session only, node not use alias
Language switcher block (content) works, content language switches.
Switching language with content translation links works but adds ?language=[langcode]
to the URL. After using content translation links language switcher (content) does not work, drupal stays on the same page (and the block on the same language).
Detection and selection (both user interface and content): Session only, node path aliased
Both Language switcher block (content) and Switching language with content translation links lead to "page not found". URL stays the same but the language changes in the switcher block.
Detection and selection (both user interface and content): URL (first) and Session (second), node path not aliased
Language switcher (content) does not work, Drupal stays on the same page (and the block on the same language).
Switching language with content translation link works, does not add anything to the URL.
Detection and selection (both user interface and content): URL (first) and Session (second), node path aliased
Language switcher (content) does not work, Drupal stays on the same page (and the block on the same language).
Switching language with content translation link works, does not add anything to the URL.
Comments
Comment #1
plachI'm pretty sure at least one of the issues you are reporting is #1294946: Language detection based on session doesn't work with URL aliases.
Comment #2
thamasThanks for pointing to that issue. I looked for realated issues, but didn't find this. I'm sure they are related but there must be something more here…
Now I tested the swithching with URL only detection method and the lang switceher block does not work with this setting too. However I discerned that it switches the default language of the site in the background. Is it the normal, expected behaviour?
Comment #3
plachAFAIK content language affects mostly the language fields are displayed in. Obviously if both UI and content language are configured to follow URL language the content language switcher will affect both fields and UI strings.
Comment #4
michaelkoehne CreditAttribution: michaelkoehne commentedYou can create a languageswitcher by yourself, here is a sample:
Comment #5
qchan CreditAttribution: qchan commentedThanks mkweb!
You saved my life.
Comment #6
thamasComment #7
SilbinaryWolf CreditAttribution: SilbinaryWolf commentedUpdated mkwebs to just return it as array data, support table prefixes (required { }) and it supports links that don't use aliases.
Comment #8
Yuri CreditAttribution: Yuri commentedAfter enabling the customized language switcher block, using code in #4 and #7, The switching does not apply the default language recognition settings. I have English as default site language, and that does not use the "/en/" url prefix.
Thus I get the error:
The requested page "/en/about" could not be found.