Project

General

Profile

Actions

Bug #97009

closed

Several LanguageService objects with different languages return the same (wrong) result

Added by Jan Delius about 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2022-02-23
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
11
PHP Version:
7.4
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Since TYPO3 11, labels are no longer cached language-specifically in the LanguageService. Until the changeover, a multi-dimensional array existed in which the first level was the respective language key. The array was replaced by the RuntimeCache in newer TYPO3 versions. Since then, the cache is filled and read independently of the language. In some cases (e.g. indexing with EXT:Solr of multilingual records) this leads to the wrong translations being returned by other LanuageService instances.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #94415: Use runtime cache for LanguageServiceClosed2021-06-25

Actions
Actions

Also available in: Atom PDF