Bug #102656
open
Exception in record history with outdated content element configuration
0%
Description
Given is a content element which is not relevant anymore and the ctype has been removed and the content element deleted.
switching to the record history brings up an exception
TCA misconfiguration in table "tt_content" field "pi_flexform" config section: ds_pointerField "list_type" points to a field name that does not exist.
Updated by Gerrit Code Review 5 months ago
- Status changed from Accepted to Under Review
Patch set 1 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
Updated by Gerrit Code Review 5 months ago
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
Updated by Christoph Lehmann 5 months ago
- Related to Bug #102655: Page history crashes - ds_pointerField "list_type" points to a field name that does not exist. added
Updated by Gerrit Code Review 3 months ago
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
Updated by Gerrit Code Review 3 months ago
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
Updated by
Updated by Daniel Schultheis about 1 month ago
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?
Updated by Gerrit Code Review 24 days ago
- Status changed from Rejected to Under Review
Patch set 1 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