Issue Bug Closed

#110262CorrelationID is not handed over for connected select / group fields

Benni Mack 07/22/26, 10:47 updated 08/11/26, 08:51

Description

Steps to reproduce

1. Log in to the TYPO3 backend as admin.
2. Create a page with two content elements (or use any existing one).
3. In the page tree, copy that page and paste it somewhere (same as an editor duplicating a page — this is one action from the editor’s perspective).
4. Inspect the history entries created by this action:

SELECT uid, tablename, recuid, actiontype, correlation_id
FROM sys_history
ORDER BY uid DESC
LIMIT 10;

Observed: The insert entry for the copied page and the insert entries for its copied content elements carry different correlation IDs (different random scope per entry), because the content elements are inserted by nested DataHandler instances that each generated their own ID.

Expected: All sys_history entries of this one copy action share the correlation scope of the outermost DataHandler instance, so RecordHistory::findEventsForCorrelation() can resolve the complete operation (e.g. for rollbacks).

Reviews 2

History 26

  1. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-07-24T13:55:10+00:00" > 07/24/26, 13:55 </span>

    Applied in changeset commit:f62f1b782f73e11da8f636f70739a24348c2c785.