Project

General

Profile

Actions
Copy link

Bug #82790

open

Finisher FormEngine definition fails with nested options

Added by Mathias Brodala about 7 years ago. Updated over 5 years ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
Candidate for patchlevel
Start date:
2017-10-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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.

Actions
Copy link
 #1

Updated by Benni Mack over 5 years ago

  • Target version changed from next-patchlevel to Candidate for patchlevel
Actions
Copy link

Also available in: Atom PDF