#82790Finisher FormEngine definition fails with nested options
Description
If a finisher is configured by nested options (similar to elements or databaseColumnMappings of the SaveToDatabase finisher), an error will occur while the FlexForm of a form plugin is being built. This causes the option in question and all other following options to be skipped entirely.
This is caused by e.g. option.nestedKey being looked up in TYPO3.CMS.Form.prototypes.standard.finishersDefinition.MyFinisher.FormEngine.elements which causes ArrayUtility::getValueByPath() to throw an exception. Due to this, no element configuration is found and the option is skipped.
As a workaround I have set the relevant options to empty values in my form definition.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 2
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2019-04-17T23:41:37+00:00" > 04/17/19, 23:41 </span>
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-10-18T16:35:03+00:00" > 10/18/26, 16:35 </span>
I think this was fixed with #86635 (548515458b6, 9.5): the FlexForm finisher sheets are now built from FormEngine.elements instead of the form definition’s options, so nested options are resolved by their full path and missing ones are skipped individually. Closing — please reopen if this still reproduces on 13.4 or later.