Task #44341: Multi Language Compatibility
Language mode "All"
|Priority:||Must have||Due date:|
|Assignee:||Dirk Hoffmann||% Done:||
|Category:||Language and Translation||Spent time:||-|
|TYPO3 Version:||4.5||PHP Version:|
There is a problem if a content is set to the language mode "All". The CE will be displayd in Page View -> Columns at default language, but not in the other languages.
Updated by Jo Hasenau over 1 year ago
- Status changed from New to Accepted
- Assignee set to Jo Hasenau
- Priority changed from Should have to Must have
Updated by Arno Dudek about 1 year ago
Still not. I think now, it's a issue of backend_layout or of the core. It comes to all CEs not only the grids.
Updated by Franz Koch about 1 year ago
I think this is a issue with tx_cms_layout. I switched from TemplaVoila back to the "traditional" page module using the backend_layout feature already some time ago, but only recently noticed on a multilingual project that elements with the sys_language_uid "-1" (all) are not displayed in other languages and that the overall language handling is somewhat awkward compared to the ease of use I knew from TemplaVoila. So I started to xclass tx_cms_layout and made it work more like TV (language wise). I also implemented copy/cut/paste buttons and a loose language binding mode that still shows translateable content elements from the default language (like possible in TV) but also allows for additional content in foreign languages. I'm quite busy atm so I hadn't found the time to finish some still missing parts, clean this thing up and create a patch for it - but if anybody is interrested I could provide my current state.
Updated by Jo Hasenau about 1 year ago
@Franz: Thanks for this confirmation. But since it actually is a core bug, I guess this would be a job for the core team then, since grid elements do not deal with the official backend layouts.
BTW: I would like to know, why you found the TV way of handling languages easy to use. After all, the problems our clients got due to TV language handling (and breaking), were one of the reasons to find another solution.
Updated by Franz Koch 12 months ago
sorry, didn't get a notification on your update/question. Well, I think language handling is easier in TV because it
- handles "language all" correctly
- when in "single language view" you can see untranslated CEs and not just a "copy all/missing" button
- it's much more flexible, so that you can have kind of a bound paradigm (due to the "untranslated content" preview), but still add CEs only for this very language.
- the "click the flag" way of translating CEs is easy to understand for editors
- the overall look and feel of the page module and translation hints is better IMO
Updated by Jo Hasenau 5 months ago
- Assignee changed from Jo Hasenau to Dirk Hoffmann
- TYPO3 Version set to 4.5