All of this assumes that multilingual content is on, input&outout encoding are set to UTF-8, and a default_language is set to a value other than 'en'
Part 'A' of issue - No matter what you select in the drop down boxes in 'translate mode', for source language, after a brief moment the 'selected value' will jump back to 'en' - HOWEVER the correct URL is generated - i.e. "...&-sourceLanguage=es"
the same behavior is exhibited for 'destination language'; No matter what is selected - the drop down box will 'snap' to English after a moment.
Part B - At this point - the behavior deviates.
IF the 'destination language' is anything OTHER than English - although the displayed value is still 'English' for Destination Langauge, the URL will be OK -
i.e "...&-sourceLanguage=es&-destinationLanguage=eu" to go from Spanish 'native' to Basque -
IF the 'destination language is English, however, you will not get a refreshed URL - you will still have only the source language in the URL. The ONLY way to get QueryTranslator to work -- where English is the destination language, is to manually change the destination language argument in the URL and refresh - you will get the 'correct form' and when it saves, the record will be written to the correct 'xxxxx_en' table.
This absolutely drove me nuts finding it...
I did not discover this bug earlier, as my test application had 'en' as the default language, and, in that case, there is never a need to select 'en' as the destination language. need better decision on how close to match all criteria.
synopsis of conf.ini
- Code: Select all
title="principalB"
multilingual_content=1
default_language = es
default_oe=UTF-8
default_ie=UTF-8
[_tables]
...
[languages]
es="Castellano"
eu="Euskara"
en="English"
fr="Français"
Thanks very much