translated content elements within gridelements have a wrong language uid
TYPO3 7.6.2 and EXT:grid_elements 7.0.4
German is the first language (uid 0), english is the second language (uid 1).
Let's say I would like to translate "page 1" with three content elements:
The first one is a normal media element,
the second one is a grid element,
the third one is a media element within the grid element
I choose "copy" as the desired translation method,
the "Record summary" for this action shows only two content elements: the first and the second content element (the third one is missing).
The first element has been copied => the language of the element has been set to english,
the second element (grid element) has been copied => the language has also been set to english,
the third element is missing.
Switching to "List Module" reveals that the third element has also been copied BUT the language (sys_language_uid) has been set to "[ INVALID VALUE ("0") ]" (expected value: 1)
Changing the value to "1" by hand brings this element back to the Page Module.
I suspect that the information about the language uid of a record gets lost in the copy process and since the "sys_language_uid" is invalid the record is not shown on the Page Module.
If you need any more information on how to replicate this, just contact me.
#1 Updated by Jo Hasenau almost 4 years ago
- Tracker changed from Bug to Support
- Category changed from Language & Translation to General Bugs
- Status changed from New to Rejected
- Assignee changed from Martin R. Krause to Jo Hasenau
- Priority changed from Must have to Won't have this time
This is a core bug which is already known to the core team and the decision was that there won't be a workaround within gridelements, since this would make things more complicated in the end.
The point is, that the core uses a simple "copy" method with this special translation action, and then assigns the language as an override value later on.
So the copy action does not know, that it is actually a translation action and therefore none of the child elements of ANY field containing relations is treated correctly.
Of course this means grid children, but it is the same problem for other relations as well.
So currently the only way to deal with this translation option is to change the values manually.