#108809Free-mode content not shown in Language Comparison Mode when default language is empty
Description
In the Page/Layout module’s Language Comparison Mode, content elements created in non-default languages using free mode ( l18n_parent = 0 ) are not displayed when the default language column contains no content elements. As a result, existing content in secondary languages is silently omitted from the comparison view.
- Create a page with multiple languages.
- Do not add any content elements in the default language.
- Add one or more content elements in a non-default language using free mode (
l18n_parent = 0). - Open the page in the Page or Layout module.
- Switch to Language Comparison Mode.
*Expected behavior*
Free-mode content elements from non-default languages are displayed even if the default language column is empty.
*Actual behavior*
No content is rendered. The comparison view remains empty.
*Technical background*
The Language Comparison template ( LanguageColumns.fluid.html ) relies on an iteration over the default language column ( <f:for each="{column.items}"> ) to create the first table row. Free-mode content is rendered exclusively during this first iteration using itemIterator.isFirst. If the default language column contains no items, the loop never executes, no initial row is created, and free-mode content from non-default languages is skipped entirely.
*Proposed solution*
Introduce a fallback rendering path that creates an initial comparison row when the default language column is empty and renders free-mode content from non-default languages, while keeping the existing behavior for connected translations unchanged.
Reviews 4
Related issues 1
Files 1
History 724
-
Gerrit Code Review pushed patch set 1 for main to change 92585 status
NewUnder Review <span data-processor="relativetime" data-value="2026-01-30T10:44:44+00:00" > 01/30/26, 10:44 </span> -
Gerrit Code Review pushed patch set 2 for main to change 92585 <span data-processor="relativetime" data-value="2026-01-30T10:47:11+00:00" > 01/30/26, 10:47 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 92585 <span data-processor="relativetime" data-value="2026-02-06T09:14:34+00:00" > 02/06/26, 09:14 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 92585 <span data-processor="relativetime" data-value="2026-02-06T09:51:17+00:00" > 02/06/26, 09:51 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 92585 <span data-processor="relativetime" data-value="2026-02-06T12:02:08+00:00" > 02/06/26, 12:02 </span>
-
Eric Harrer commented and changed attached image (1).png <span data-processor="relativetime" data-value="2026-03-06T11:44:47+00:00" > 03/06/26, 11:44 </span>
Today, we explicitly tested the functionality of sorting in non-default-language columns for this patch in the backend. The sorting works without any problems.
image%20%281%29.png
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-03-31T09:05:30+00:00" > 03/31/26, 09:05 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:50+00:00" > 04/21/26, 11:23 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 92585 <span data-processor="relativetime" data-value="2026-04-22T07:20:56+00:00" > 04/22/26, 07:20 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 92585 <span data-processor="relativetime" data-value="2026-04-23T10:50:09+00:00" > 04/23/26, 10:50 </span>
-
Eric Harrer changed target version TYPO3 Version
1415 <span data-processor="relativetime" data-value="2026-04-24T06:21:15+00:00" > 04/24/26, 06:21 </span> -
Denis Mir changed Related to #110275 <span data-processor="relativetime" data-value="2026-07-23T13:30:05+00:00" > 07/23/26, 13:30 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 95170 <span data-processor="relativetime" data-value="2026-08-07T19:16:38+00:00" > 08/07/26, 19:16 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 95170 <span data-processor="relativetime" data-value="2026-08-07T19:20:13+00:00" > 08/07/26, 19:20 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 95170 <span data-processor="relativetime" data-value="2026-08-08T11:06:39+00:00" > 08/08/26, 11:06 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 95199 <span data-processor="relativetime" data-value="2026-08-10T08:20:05+00:00" > 08/10/26, 08:20 </span>
-
Gerrit Code Review pushed patch set 2 for 14.3 to change 95199 <span data-processor="relativetime" data-value="2026-08-10T11:31:17+00:00" > 08/10/26, 11:31 </span>
-
Gerrit Code Review pushed patch set 3 for 14.3 to change 95199 <span data-processor="relativetime" data-value="2026-08-10T17:28:08+00:00" > 08/10/26, 17:28 </span>
-
Gerrit Code Review pushed patch set 4 for 14.3 to change 95199 <span data-processor="relativetime" data-value="2026-08-10T18:46:10+00:00" > 08/10/26, 18:46 </span>
-
Gerrit Code Review pushed patch set 5 for 14.3 to change 95199 <span data-processor="relativetime" data-value="2026-08-10T19:08:43+00:00" > 08/10/26, 19:08 </span>
-
Gerrit Code Review pushed patch set 6 for 14.3 to change 95199 <span data-processor="relativetime" data-value="2026-08-10T19:22:06+00:00" > 08/10/26, 19:22 </span>
-
Gerrit Code Review pushed patch set 7 for 14.3 to change 95199 <span data-processor="relativetime" data-value="2026-08-10T19:32:17+00:00" > 08/10/26, 19:32 </span>
-
Marcel Küpper commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-08-10T20:00:09+00:00" > 08/10/26, 20:00 </span>Applied in changeset commit:24f33e7def6d5589e933abb5d279eb3320c95266.
This behavior is related to the v14 change described in https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/14.0/Important-106649-DefaultLanguageBindingInPageModule.html.
With TYPO3 v14, the Page/Layout module always uses default-language binding in Language Comparison mode once multiple languages are active. This exposed an unhandled edge case when the default language column contains no records.
The proposed fix does not reintroduce the former v13 behavior, but adds a missing fallback for this specific situation within the current v14 rendering logic.