TYPO3 Core

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82174

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82174

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/82174

Is there a specific reason why this issue has been rejected and won't be fixed?

I've stumbled into the exact same problem where a content element that utilized the pi_flexform field has first been edited and later was deleted now throwing this exception when the history view is opened.

It looks like FlexFormValueFormatter::format() which is called in the process is still continuing with the formatting logic although BackendUtility::getRecord() could not retrieve a record as it had already been deleted.

Should FlexFormValueFormatter::format() then not just return an empty string instead of trying to retrieve the flexform data-structure from a non-existing record leading to the exception mentioned here?