Issue Bug Closed

#110524impexp: page translations are imported with a wrong pid

Benjamin Kott 08/24/26, 10:34 updated 11/07/26, 22:11

Description

When a page tree with translated pages is exported and imported again, every page
translation is created directly on the import target instead of on the page its
“l10n_parent” lives on. The default language pages keep their parent, the
translations do not.

This breaks what the core documents itself: a default language record and all its
translations must be on the same page.

Reproduction

The core ships an export file with the relevant shape – it is the expected output
of the existing export test:

typo3/sysext/impexp/Tests/Functional/Fixtures/XmlExports/pages-and-ttcontent-multilingual.xml

Import it into an installation with an empty page tree:

typo3 impexp:import <path>/pages-and-ttcontent-multilingual.xml 0

Expected: every page keeps the parent it has in the file. Pages 8, 9 and 10 are
translations with pid=1 and l10n_parent 5, 5 and 7, all of them on the imported
root page.

Actual: pages 1 to 7 are placed correctly, pages 8, 9 and 10 end up on pid 0.
Only the pid is wrong, l10n_parent is mapped correctly. The frontend still
resolves the pages, since overlays are found through l10n_parent – the page tree
in the backend is where it is visibly wrong.

Affected versions

Reproduced at runtime on 14.3.6 and against current main (15.0.0-dev). The
relevant code is identical on 13.4.

Reviews 3

History 38

  1. Benjamin Kott commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-02T22:05:09+00:00" > 09/02/26, 22:05 </span>

    Applied in changeset commit:ef54b324dd0417607c83de65c3b7f84160948787.

  2. Gerrit Code Review pushed patch set 1 for 13.4 to change 96712 status Resolved Under Review <span data-processor="relativetime" data-value="2026-10-15T08:18:29+00:00" > 10/15/26, 08:18 </span>

  3. Benni Mack commented and changed status Under Review Closed <span data-processor="relativetime" data-value="2026-11-07T22:11:46+00:00" > 11/07/26, 22:11 </span>

    fixed in v14+, closing this again, as the v13 change was abandoned.