Project

General

Profile

Actions

Task #88494

closed

Drop DB field t3_origuid / "origUid" functionality

Added by Oliver Hader almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-06-05
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

The special TCA value / DB field "origUid" (usually "t3_origuid") has
had a long run, and it was used for various places, making the
value of the data very ambiguous, non-predictable and thus,
not usable for further usages.

One usage was to copy a record, where origUid contained the value of
the original record - without further evaluation.

Since localizations ("localize" and "copy into language") internally
are using previously mentioned copy process, origUid contained the
value of the original translation - however not very reliable since
consecutive localize & copy processes did not maintain integrity in a
proper way. That's the reason why "translationSource" ("l10n_source")
has been introduced with TYPO3 v8 already.

Additionally, versioning used it to store the original "online ID"
which is contained within "t3ver_oid" as well.

Using the field in any extension for further usage is not recommended,
as it was never clear what the meaning of the value was.

Since the versioning/workspaces and translation handling
implemented properly, this field is filled, but has no real
use anymore - it is now removed.


Subtasks 2 (0 open2 closed)

Task #88495: Drop t3_origuid fields from functional testsClosed2019-06-05

Actions
Task #88501: Revert dropping t3_origuid from functional testsClosed2019-06-06

Actions

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #103099: Reduce TCA ctrl origUid usagesResolved2024-02-11

Actions
Actions

Also available in: Atom PDF