Issue Bug Resolved

#97178Translation of a record with FAL relation not possible after language change from "-1 all" to "0 default"

Stephan Brun 03/14/22, 07:59 updated 10/17/26, 12:35

Description

The translation of a record which was created with language “-1 all” and a FAL media relation and set later to language “0 default” is not possible. The error message in the backend is “503 Child record was not processed”.

Steps to reproduce:
1. Create a news record with language “-1 all“
2. Add a FAL Media and save record
3. Change language of the news record to “0 default” and save again.
4. Translate the news record to any other language eg. 1

I think the problem is that the fal relation in the database still has the languag “-1 all”.

Tested with TYPO3 v11.5.8 and News 9.3.0, but it will happen also with all other relations.

Reviews 2

History 511

  1. Floyd Hermes commented <span data-processor="relativetime" data-value="2024-08-29T09:08:56+00:00" > 08/29/24, 09:08 </span>

    The error can be consistently reproduced. However, an additional issue occurs because the system duplicates the image multiple times.
    When the user repeatedly clicks the “translate” button (due to the translation function not working properly), the system generates thousands of duplicated images.
    This problem significantly impacts system stability.

  2. Alex Kellner commented <span data-processor="relativetime" data-value="2025-11-03T09:40:48+00:00" > 11/03/25, 09:40 </span>

    I can confirm this bug in TYPO3 13.4.18 (together with tt_address 9.1.0).

    How to reproduce here:
    • Adding a new tt_address record and set tt_address.sys_language_uid=-1
    • Add an image to tt_address (also the file reference gets sys_file_reference.sys_language_uid=-1)
    • After that changing tt_address record to default language (tt_address.sys_language_uid=0)
    • Checking in database that the reference language didn’t changed (is still -1)
    • Now, when trying to localize the address record in list view, an exception occured

    The error message:

    (1/1) #1486233164 RuntimeException
    
    Child record was not processed
  3. Gerrit Code Review pushed patch set 13 for main to change 87595 status New Under Review <span data-processor="relativetime" data-value="2026-10-13T20:00:53+00:00" > 10/13/26, 20:00 </span>

  4. 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.