Issue Bug Closed

#110608Hand the correlation id over to the remaining history writers

Benni Mack 09/02/26, 19:46 updated 09/08/26, 10:03

Description

Since #110586 and #110588 every history writer that belongs to a DataHandler operation writes under that operation’s correlation scope — except three. ExtbaseHistoryTracker passes no correlation id at all, so its entries fall back to a scope-less id derived from the record alone. DataHandlerInternalWorkspaceTablesHook discards all records of a deleted workspace through a fresh data handler, and EditDocumentController runs “save and duplicate” as a second data handler; both start their own random scope instead of continuing the one they belong to.

Hand the correlation id of the surrounding operation over in all three places, so a scope can finally be used to group the history entries of one operation. Extbase has no data handler run to inherit from, so the tracker creates one scope per request and reuses it for every entry it writes.

Reviews 2

History 26

  1. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-04T09:00:11+00:00" > 09/04/26, 09:00 </span>

    Applied in changeset commit:3ed962f7a5f86726ae60af924506062f676c03e1.