Issue Feature Under Review Orphaned

#109332Introduce AfterHistoryDataCollectedForRecordEvent PSR-14 event in RecordHistory

Amir Arends 03/24/26, 07:23 updated 03/24/26, 08:42

Description

Problem

`RecordHistory::getHistoryDataForRecord()` collects history entries for a given record, but there is currently no way for extensions to augment or extend this history data without overriding the class via Xclass. This is limiting in cases where related records are linked through a custom foreign-key field rather than pid. For example, records which are referenced over an inline field are invisible in the history view because the core logic only follows pid-based sub-entries.

Solution

Introduce a new PSR-14 event `AfterHistoryDataCollectedForRecordEvent` dispatched at the end of `RecordHistory::getHistoryDataForRecord()`, after all core history data has been collected but before the result is sorted and returned.

Impact

  • New event class: TYPO3\CMS\Backend\History\Event\AfterHistoryDataCollectedForRecordEvent
  • Small, non-breaking change to RecordHistory::getHistoryDataForRecord()

Reviews 1

History 13

  1. Garvin Hicking changed subject [FERATURE] Introduce AfterHistoryDataCollectedForRecordEvent PSR-14 event in RecordHistory Introduce AfterHistoryDataCollectedForRecordEvent PSR-14 event in RecordHistory category <span data-processor="relativetime" data-value="2026-03-24T08:42:17+00:00" > 03/24/26, 08:42 </span>