#78642Improve t3_origuid handling
Description
1. The purpose and usage of the t3_origuid should be claryfied.
2. The field needs to be covered with tests in live and workspaces.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Subtasks 5
- Task #78303cover tt_content t3_origuid field in datahandler functional tests
- Task #78382Workspaces functional tests should cover t3_origuid field
- Task #78597Functional tests for t3_origuid in workspaces/publish
- Task #78637Functional tests for t3_origuid in workspaces/publishAll
- Bug #78643workspace operations are setting t3_origuid but shouldn't
Related issues 3
History 4
-
Christian Kuhn changed Related to #103099 <span data-processor="relativetime" data-value="2026-03-17T09:14:12+00:00" > 03/17/26, 09:14 </span>
-
Christian Kuhn commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-03-17T09:15:35+00:00" > 03/17/26, 09:15 </span> -
Christian Kuhn changed Related to #90997 <span data-processor="relativetime" data-value="2026-03-17T09:17:00+00:00" > 03/17/26, 09:17 </span>
-
Christian Kuhn changed Related to #88063 <span data-processor="relativetime" data-value="2026-03-17T09:17:09+00:00" > 03/17/26, 09:17 </span>
Hey. t3_origuid is by now only used for ‘monoglot’ dependencies: when an inline parent is language aware, and a child is not. There are still issues with this construct, but I’d say the main request of this issue has been solved for now. As such, I’ll close here.