Issue Bug Closed

#110275Free-mode language columns are misaligned by forced default-language binding in the Layout module

Denis Mir 07/23/26, 13:21 updated 08/11/26, 08:51

Description

Since the removal of mod.web_layout.defLangBinding and the permanent enabling of default-language binding in the Layout module (Important-106649), the Language Comparison view is broken for languages that use free translation mode (content elements with l18n_parent = 0).

The comparison grid builds one table row per default-language content element and can only attach a translation to such a row when the translated element is connected (l18n_parent pointing at the default record). Free-mode content has no default-language parent, so it cannot be aligned into its own rows. As a result every free-mode content element of a colPos is dumped into a single cell in the first default-language row, and the translation column no longer corresponds row-by-row to the default column. Editors can no longer place two languages side by side for comparison, which is the entire purpose of the mode.

The pending patch Gerrit 92585 (#108809) only fixes the sub-case where free-mode content vanishes when the default column is empty; it does not address the general free-mode grid misalignment reported here.

Steps to reproduce

  1. Site with a default language (e.g. English) and a second language (e.g. Bulgarian).
  2. On a page, create content in the second language in free mode, ideally a nested structure (e.g. a container/section element with children).
  3. Open the page in the Layout module and switch to Language Comparison with both languages selected.

Expected behavior

As in v12/v13 LTS: each free-mode language is rendered as its own, independent, fully structured column next to the default language, so both languages can be read and compared side by side (see attached screenshot 12_13LTS.png).

Actual behavior

  • All free-mode content of a colPos is squeezed into the first default-language row; the rest of the default column has no counterpart, and the columns diverge badly (see attached screenshot 14LTS.png).
  • If the default-language column of a colPos is empty, free-mode content of that colPos is not rendered at all (partly addressed by #108809).

Technical analysis (v14.3.5, typo3/cms-backend)

The default-language binding is now unconditional — defLangBinding / defaultLanguageBinding no longer exist anywhere in cms-backend. Two locations implement the hardcoded binding:

  1. Classes/View/Drawing/BackendLayoutRenderer.php → getLanguageColumnsForPageLayoutContext() (L177–240). Rows are built from the default column; a translation is attached to a default row only when mode = 'connected'@ (L216) via @l18n_parent = defaultUid (L220, addTranslation() L223). The default column is always returned at index 0 (L239) as the alignment anchor.
  2. Resources/Private/Partials/PageLayout/LanguageColumns.fluid.html (L79–153). One <tr> per default item (L95–96). For non-connected columns the <f:else> branch (L115–123) dumps all free items into a single cell of the first default row (itemIterator.isFirst, L116); if the default column is empty, the outer loop never runs and free content is not rendered.

Mode is derived purely from l18n_parent in Classes/View/BackendLayout/ContentFetcher.php → getTranslationData() (free L169, connected L173, mixed L199–202).

Free-mode (and mixed-mode) language columns need to be rendered as their own independent column of rows, decoupled from the default-language row anchor, while keeping connected-mode row binding intact.

Related

  • Relates to #106649 (cause: forced default-language binding)
  • Relates to #108809 / Gerrit 92585 (fixes only the empty-default sub-case)

Reviews 3