---
title: "Important: #89672 - transOrigPointerField is not longer allowed to be excluded"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:important-89672"
source: "Changelog/10.3/Important-89672-TransOrigPointerFieldIsNotLongerAllowedToBeExcluded.rst"
typo3-version: "10.3"
typo3-major: 10
type: "important"
issue: 89672
forge: "https://forge.typo3.org/issues/89672"
tags: ["Backend", "Database", "TCA", "ext:core"]
rendered: "2026-09-17T12:41:04+00:00"
---

# Important: #89672 - transOrigPointerField is not longer allowed to be excluded {#important-89672-transorigpointerfield-is-not-longer-allowed-to-be-excluded}

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

## Description {#description}

The configured `$GLOBALS['TCA'][$table]['ctrl']['transOrigPointerField']`
can now not longer be excluded as this leads to inconsistent data stored in the
database. This happens when a non-admin user creates a localization by not having
the permission to edit the `transOrigPointerField`. Usually this is the
`l10n_parent` or `l18n_parent` field.

A migration wizard is available that removes the option from your TCA and adds a
deprecation message to the deprecation log where code adaption has to take place.