Project

General

Profile

Actions

Bug #79412

closed

Epic #77909: Enhance EXT:form

Feature #77910: Introduce new form framework

Ext:form - Finisher dies on parseOption if a formvalue should be used which is not a string

Added by Ralf Zimmermann almost 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
Form Framework
Target version:
-
Start date:
2017-01-22
Due date:
% Done:

100%

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

Description

You can encapsulate a finisher option value with {}.
This enables you to access every getable property from the TYPO3\CMS\Form\Domain\Runtime.
For example you can set the "subject" option value from the EmailToSender finisher to something like {textfield-1}.
If you do so, the subject option value will be filled with the submitted data from the formelement with the identifier 'textfield-1'.
This is done by the function TYPO3\CMS\Form\Domain\Finishers\AbstractFinisher::parseOption().
parseOption fails if such a referenced formelement value contains non text value like a DateTime object.
This happens if a formelement do some property mapping stuff.
With this patchset, parseOption replace finisher option values with formelement values only if the formelement value is a string.
In addition, this enables you to replace non text values with your custom finisher implementations.

Actions

Also available in: Atom PDF