Issue Bug Resolved

#111329Extbase ignores records without default language record in fallback mode

Benni Mack 11/03/26, 11:30 updated 11/06/26, 20:05

Description

With fallbackType “fallback” (LanguageAspect::OVERLAYS_MIXED), Extbase repositories do not return records of the requested language that have no default language record (“floating” records, l10n_parent = 0).

The TypoScript content object CONTENT and PageRepository include these records for both “fallback” and “strict”. Extbase only includes them for “strict” (OVERLAYS_ON_WITH_FLOATING), see #89131 / #87160.

Example: a news record created directly in German (no default language parent) is shown on a German page with fallbackType “strict”, and with fallbackType “fallback” in a CONTENT element, but not in an Extbase plugin with fallbackType “fallback”. Query count() is affected as well.

The functional tests already document this difference: ReadingTranslationsTest::readingAllPostsWithOverlaysMixedByExtbase() and countingPostsWithOverlaysMixedByExtbase() are skipped with “Extbase differs from core”, and TranslatedSiteContentTest expects these records to be hidden in Extbase while the frontend LocalizedSiteContentRenderingTest with the same fixtures expects them to be shown.

Extbase should include floating records for OVERLAYS_MIXED as well, so Extbase and TypoScript return the same records.

Reviews 1

History 12

  1. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-06T20:05:11+00:00" > 11/06/26, 20:05 </span>

    Applied in changeset commit:8c68fe0b52133b5a93a8b72709d2d4f59b56471b.