Bug #103969
Updated by Daniel Siepmann 26 days ago
Steps to reproduce:
# Create a site with at least two language
# Create a page within the site
# Create translation of the new page
# Create a content element in default language (don't save yet)
# Switch language of content element to all languages (-1) and save
# Attach a file relation and save. The relation will be saved with -1 for languages, which can be confirmed by <code>select sys_language_uid from sys_file_reference</code> once saved.
# Switch language of content element to default language 0 and save.
Result:
The relation will still have -1, which is out of sync with the parent element. But that might be okay, I'm not sure about the expectation and concept.
Now continuo:
# Create translation of the content element
Expectation:
The content element will be translated, with the file relation.
Actual:
The content element is translated, but the translation has two file relations.
The -1 and a translated one.
The behaviour is slightly different for EXT:news and inline content elements. Follow the same steps but create a content element within a news record instead of a file relation. Tested with EXT:news version 11.4.2.
Expectation: The news record will be translated, with content element.
Actual:
An Exception is thrown:
<pre>
(1/1) #1486233164 RuntimeException
Child record was not processed
</pre>
I've attached a sqlite file with the base situation where one can reproduce the issue by triggering the corresponding localizations of records.
I don't know what the expected behaviour should be, maybe synchronize the sys_language_uid field upon change? But definitely hot throwing an exception while translating.
Workaround: Manually switch languages of all relations. But that's not possible for file relations by default as the field is not rendered.