Issue Task Resolved

#111055Test Extbase against core for fields with l10n_mode exclude

Alexander Schnitzler 10/14/26, 14:04 updated 10/15/26, 22:40

Description

Fields configured as 'l10n_mode' => 'exclude' belong to the default language record. DataHandler keeps them in sync: it writes the value of the default language record into every translation, gives every translation its own copy of each child of an excluded inline relation, synchronizes excluded MM relations, and drops excluded values submitted on a translation. Core reads a translation’s values and relations from the translation itself.

Extbase does not evaluate l10n_mode at all. There is no test that shows where it matches core and where it does not.

Proposal

Add a functional test that runs every scenario twice against the same expected result: once through core (DataHandler for writes, PageRepository overlay plus the Record API for reads) and once through Extbase. Core must pass, so the expectation is proven. Where Extbase fails, the test shows the difference as text, e.g.

-post 2 [de] "Hallo Welt": author Ben, ...
+post 2 [de] "Hallo Welt": author Anna, ...

The blog_example fixture extension gets l10n_mode => exclude on post.date, author, reviewer, tags, comments and additional_info. Neither Extbase nor PageRepository evaluates l10n_mode on reads, so existing tests are not affected.

Covered scenarios

  • Reading a translation: excluded values, children of excluded inline relations, excluded MM relation, query by an excluded property
  • Writing the default language record: excluded value, translatable value, adding and removing children of excluded inline relations, excluded MM relation, history, workspace
  • Writing through a translation: excluded value, translatable value, children and MM relation

Current differences between Extbase and core

  • Changes of excluded values, children and MM relations on the default language record do not reach the translations.
  • Excluded values, children and MM relations changed through a translation are written instead of dropped. Removing a tag through a translation even changes the default language record.
  • Only the default language record gets a history entry.
  • In a workspace, Extbase writes the live record instead of creating versions of the default language record and its translations.
  • With overlays “on”, Extbase drops related records without a translation (persons, tags), while core resolves them.

The failing Extbase tests are skipped and reference this issue, so they can be enabled once Extbase follows core.

Reviews 2

History 25

  1. Anonymous commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-10-15T22:40:16+00:00" > 10/15/26, 22:40 </span>

    Applied in changeset commit:f8b8ae65b767ac1afd7a116843be5cbdcc0bd18d.