Review main Work in progress Breaking

97455[!!!][FEATURE] Introduce language fallback type "connected"

Benni Mack CR 0 V 0 Expert +1292 −182 updated 11/17/26, 20:15

Commit message

The fallback types "strict" and "fallback" only differ in whether
untranslated content elements are shown in the default language,
while the fallback chain decides for pages. Page links ignore the
chain. This leads to combinations where pages are rendered but not
linked, or linked but not found, and Extbase used the fallback chain
for records differently than TypoScript.

The new fallback type "connected" lets the fallback chain decide for
pages, content elements and links alike: "0" in the chain means
"fall back to the default language". "free" stays as it is.

- SiteLanguage converts "strict" and "fallback" to "connected" when
  the site configuration is read, and adapts the fallback chain so
  that translated pages are rendered as before. A missing fallback
  type means "connected".
- LanguageAspectFactory maps "connected" to the overlay type "mixed"
  if the default language is part of the fallback chain, otherwise
  to "includeFloating".
- A translation that exists but is not visible, for example a hidden
  translation, stops the fallback chain in PageRepository and Extbase:
  the record is not shown. A translation that does not exist lets the
  chain continue.
- PageLinkBuilder only links pages that are rendered in the target
  language.
- Extbase selects records of the default language that are translated
  into a language of the fallback chain, as TypoScript does.
- The site module offers "connected" and "free", and shows former
  configurations converted.
- The status report lists site languages that still use "strict" or
  "fallback" in their configuration file.

The changelog entries also describe how connected and free mode
work, as the reference for future changes.

Test this change

Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch

Check out patch set 7
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/55/97455/7 && git checkout FETCH_HEAD
Cherry-pick onto main
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/55/97455/7 && git cherry-pick FETCH_HEAD

Review

  • Code review CR 0 Needs a vote
  • Verified V 0 Needs a vote
    • core-ci +1 CI

Merge conflicts 16

Issues 2

Files 29

Show 9 more files

Review log 714

  1. Benni Mack uploaded patch set 1 11/09/26, 17:12

  2. core-ci voted on patch set 1 V -1 11/09/26, 17:27 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/113743

  3. Benni Mack uploaded patch set 2 V -1 11/09/26, 17:56

  4. core-ci voted on patch set 2 V -1 11/09/26, 18:25 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/113750

  5. Benni Mack rebased onto patch set 3 V -1 11/09/26, 19:20

  6. core-ci voted on patch set 3 V -1 11/09/26, 19:33 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/113768

  7. Benni Mack uploaded patch set 4 V -1 11/09/26, 21:14

  8. core-ci voted on patch set 4 V -1 11/09/26, 21:34 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/113795

  9. Benni Mack rebased onto patch set 5 V -1 11/11/26, 10:27

  10. core-ci voted on patch set 5 V -1 11/11/26, 10:53 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114047

  11. Benni Mack uploaded patch set 6 V -1 11/17/26, 18:49

  12. core-ci voted on patch set 6 V -1 11/17/26, 19:05 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114778

  13. Benni Mack rebased onto patch set 7 V -1 11/17/26, 20:05

  14. core-ci voted on patch set 7 V +1 11/17/26, 20:15 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114787