Issue Bug Resolved

#103969Update language of inline elements is missing, leading to follow up issues

Daniel Siepmann 06/04/24, 06:04 updated 10/17/26, 12:35

Description

Steps to reproduce:

  1. Create a site with at least two language
  2. Create a page within the site
  3. Create translation of the new page
  4. Create a content element in default language (don’t save yet)
  5. Switch language of content element to all languages (-1) and save
  6. Attach a file relation and save. The relation will be saved with -1 for languages, which can be confirmed by select sys_language_uid from sys_file_reference once saved.
  7. 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:

  1. 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:

(1/1) #1486233164 RuntimeException

Child record was not processed

This is due to ['behaviour']['allowLanguageSynchronization' => true, within EXT:news. Removing this option results in same behaviour as for tt_content images.

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.

When this happens: E.g. when following #103970 because the relations are than initially stored with a different language value than their parent.

Reviews 2

Files 1

History 1533

Show 8 earlier messages
  1. Sybille Peters commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-10-17T12:35:14+00:00" > 10/17/26, 12:35 </span>

    Applied in changeset commit:c4c5e37ff8f8d7ef215a16228c47006ad844a346.