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?

Sorry to bother again but are there any updates on this issue as it has been under review for two months now.

There's been an implementation of a patch in the linked Gerrit patch tracker: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83648

You could help push things forward if you are able to test the patch and give feedback if it helps you, ideally directly in the Gerrit tracker via voting.

Since this is an OpenSource project it sadly happens that issues stall and the people implementing bug fixes may not be able to keep up. In that case, any help is appreciated :-)

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/+/83648

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/+/83648

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

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

Hi guys,

we stumbled up on the same problem and without looking for the solution we found that the getRecord supports using $useDeleteClause = false . We tried using it that way and with that the history can also show the plugin options changes again.

I don't know if we are too late here, but I guess that would be a 'better' solution?

Maybe someone can have a look at that and decide whether that would be better:

# typo3/cms-backend/Classes/View/ValueFormatter/FlexFormValueFormatter.php:48
$record = BackendUtility::getRecord($tableName, $uid, '*', '', false) ?? [];

Cheers,
Diego

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

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