Issue Bug Under Review Regression

#111422Translation wizard ignores columns added via AfterPageColumnsSelectedForLocalizationEvent

Marc Fink 11/12/26, 12:16 updated 11/16/26, 08:19

Description

Environment

- TYPO3 14.3.10 (code unchanged on ‘main’ as of 2026-11-12)
- Reproduced with EXT:flux 12.0.2, which stores nested content in colPos values outside the page’s backend layout
(parent uid * 100 + column) and adds those columns via AfterPageColumnsSelectedForLocalizationEvent

Steps to reproduce

1. Page with two languages. All content in the backend layout’s columns is already translated.
2. Add an element in the default language whose ‘colPos’ is not part of the page’s backend layout, and add that
column through a listener for AfterPageColumnsSelectedForLocalizationEvent (as EXT:flux does for nested content).
3. Page module → “Translate” → choose target and source language.

Expected

The content selection step lists the untranslated element, like the TYPO3 13 wizard did.

Actual

The step shows “This page does not contain any content elements.” and the element cannot be selected, so it cannot be
translated with the wizard.

The response of /typo3/ajax/wizard/localization/content contains the records in the count but not in the layout;
on our page ‘elementCount: 20’ while the ‘records’ arrays of both backend layout columns are empty. Because ‘elementCount’ is not 0, the step does not
auto-advance either; it stops with the message.

Cause

LocalizationController::getContent() (EXT:backend/Classes/Controller/Wizard/LocalizationController.php, 14.3.10)
collects the records per colPos and dispatches AfterPageColumnsSelectedForLocalizationEvent and
@AfterRecordSummaryForLocalizationEvent@. buildLayoutStructure() then only iterates
@$backendLayout->getStructure()[‘__config’][‘backend_layout.’][‘rows.’]@. Records and columns that are not part of the
backend layout are dropped; $columns is only used for labels. The event also receives an empty columnList, which
nothing reads anymore.

The ‘content-record-selection-step’ shows the “no content” message when the rendered layout contains no records
(getAllRecordUids() only walks layout.rows).

In TYPO3 13, the wizard rendered the columns from the event’s result (‘columns’ / ‘columnList’ in ‘localization.ts’),
so extension-provided columns were listed. This is a regression for extensions that use colPos values outside the
backend layout (EXT:flux; possibly also EXT:container, whose README states that child elements are not listed in the
translation dialog; not verified by us).

Suggested fix

Render columns returned by the event that are not part of the backend layout, e.g. as an additional row after the
backend layout rows (position = colPos, label from $columns, records from $records[$colPos]), or at least
include records whose colPos is not part of the layout in such an extra row.

Workaround

A listener for AfterRecordSummaryForLocalizationEvent that moves the records into a column of the backend layout
(we place nested records in the page column of their outermost container).

Reviews 1

History 12

  1. Marc Fink changed subject # Translation wizard ignores columns added via AfterPageColumnsSelectedForLocalizationEvent Translation wizard ignores columns added via AfterPageColumnsSelectedForLocalizationEvent <span data-processor="relativetime" data-value="2026-11-12T12:28:59+00:00" > 11/12/26, 12:28 </span>