Bug #88622

LanguageAspect::getLegacyLanguageMode returns different result since 9.5.6

Added by Markus Opahle 5 months ago. Updated about 1 month ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2019-06-24
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Example Site Configuration:


rootPageId: 2
base: 'http://localhost/'
baseVariants: {  }
languages:
  -
    title: Deutsch
    enabled: true
    languageId: '0'
    base: /
    typo3Language: de
    locale: de_DE.utf-8
    iso-639-1: de
    navigationTitle: ''
    hreflang: ''
    direction: ''
    flag: de
  -
    title: English
    enabled: true
    languageId: '1'
    base: /en/
    typo3Language: default
    locale: en_US.utf-8
    iso-639-1: en
    navigationTitle: ''
    hreflang: ''
    direction: ''
    fallbackType: strict
    fallbacks: ''
    flag: gb

Steps to reproduce:
  1. use LanguageAspectFactory::createFromSiteLanguage() to create a LanguageAspect from the config above
  2. call LanguageAspect::getLegacyLanguageMode

Expected result (as it was in 9.5.5 and before):
strict

Current result (9.5.6 and 9.5.7)
content_fallback

This affects how extbase handles translated records if you disable consistentTranslationOverlayHandling (see \TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbQueryParser::getSysLanguageStatement)

History

#1 Updated by Christian Eßl about 1 month ago

  • Category set to Link Handling, Site Handling & Routing

Also available in: Atom PDF