Hi, great module. This is the way it should have been from the beginning! It also makes the translator's work much easier. I have been playing around with this module and so far I encountered only this problem:
If source node is not written in the default language of my site, I am not able to translate the menu title of that language.
Example: I have site in English, Spanish, Italian, Portuguese, and French. Spanish is the default language. I create a source node in English and enable menu title translation. I can then add tranlations of menu title into all other languages, except for Spanish, which is default language. When I edit the Spanish node, I can write the translation of menu title and save, but when I go back I still see the original text in English. For the other node translations there is no problem.
In language settings I have ""All content. No language conditions apply." And the menu item of the source nodes are set to "All languages".
Normally, people would first write all content in default language, and then translate to other languages, but in beginning we changed the default language, so that's why not all sources are in same language. I hope there will be a solution for this. Otherwise, can someone tell me an easy way to switch source language to default language for all nodes with menu links?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | i18nmenu_node-877378-5.patch | 1.07 KB | plach |
Comments
Comment #1
miro_dietikerI see this issue...
Skimming though the code i actually didn't find a quick reason why it doesn't consider translation into default language.
plach, can you help us? Since i18n allows to dis-/enable translation for virtually every language (including default language) we should explicitly allow this too.
It is a common situation to add sources of foreign languages to a system.
Lars -- did you enable the variable to enable default language translation? See the code in i18nstrings...
Please check and report again!
Plach, we should document this in the README / project frontpage if needed.
Comment #2
LarsKramer commentedThanks a lot. I added the string to my settings.php and now it seems to work. Had never heard about that variable, and ordinary node translation to default language worked fine before.
Comment #3
plachSorry, didn't have time to give a look at this yet. The approach proposed in #3 is right, I'll try to update documentation and code (if needed) ASAP.
Comment #4
plachComment #5
plachCommitted the attached patch to HEAD.