---
title: "Important: #93765 - Extbase identity map now language-aware"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:important-93765-1738100000"
source: "Changelog/14.2/Important-93765-ExtbaseIdentityMapNowLanguageAware.rst"
typo3-version: "14.2"
typo3-major: 14
type: "important"
issue: 93765
forge: "https://forge.typo3.org/issues/93765"
tags: ["PHP-API", "ext:extbase"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Important: #93765 - Extbase identity map now language-aware {#important-93765-1738100000}

See [forge#93765](https://forge.typo3.org/issues/93765)

## Description {#description}

The Extbase persistence session's identity map now includes language context
when domain objects are cached. Previously, the identity map used identifiers
based only on a record's UID and localized UID, which could cause incorrect
translations to be returned when the same object was accessed by different
`LanguageAspect` configuration inside the same request.

The identity map identifier now includes the language context,
specifically the `contentId`, `overlayType`, and `fallbackChain`
properties of `LanguageAspect`.

## Impact {#impact}

This change ensures that objects loaded with different language configurations
are cached separately in the identity map. For example, if an object is first
loaded with `OVERLAYS_ON` and then queried again with `OVERLAYS_MIXED`,
the system will correctly return different cached objects for each context.

The change is transparent for most use cases. However, objects retrieved with
different language settings are now distinct instances. Code relying on
object identity (for example, using `===` comparison) between objects loaded
with different language settings will need adjustment.