#97863EXT: form - do not send email notification by EmailToReceiver
Description
Related to #83010
I have the similiar problem with TYPO3 11, while I tried to use a form with an AJAX-request. The finisher for sending of emails would work sometimes; and sometimes it would not work. After a lot of poking around, I found out:
The following version in the template of the form prohibited the sending of mails in my case:
<f:form.textfield
value="{myLink}"
name="{element.identifier}"
id="{element.uniqueIdentifier}"
errorClass="{element.properties.elementErrorClassAttribute}"
additionalAttributes="{formvh:translateElementProperty(element: element, property: 'fluidAdditionalAttributes')}"
/>
The following version performed the sending of mails in my case:
<f:form.textfield
value="{myLink}"
property="{element.identifier}"
id="{element.uniqueIdentifier}"
errorClass="{element.properties.elementErrorClassAttribute}"
additionalAttributes="{formvh:translateElementProperty(element: element, property: 'fluidAdditionalAttributes')}"
/>
The line property="{element.identifier}" is the difference.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 5
-
Björn Jacob changed description <span data-processor="relativetime" data-value="2022-07-06T16:26:16+00:00" > 07/06/22, 16:26 </span>
-
Benni Mack changed Sprint Focus
Remote SprintOn Location Sprint <span data-processor="relativetime" data-value="2023-08-02T14:48:06+00:00" > 08/02/23, 14:48 </span> -
Simon Schaufelberger commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-02-14T00:07:37+00:00" > 02/14/26, 00:07 </span> -
Georg Ringer changed Sprint Focus
On Location Sprint<span data-processor="relativetime" data-value="2026-08-06T15:48:13+00:00" > 08/06/26, 15:48 </span> -
Georg Ringer commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-10-06T17:05:23+00:00" > 10/06/26, 17:05 </span>Closing this issue, as it is caused by the custom template rather than by EXT:form. With
name="{element.identifier}"the field is rendered astx_form_formframework[<element>]instead oftx_form_formframework[<form>][<element>], so the value never reaches the form runtime. A required field then fails validation and no finisher is executed. All templates shipped with EXT:form use property=”{element.identifier}”, which is the correct way in custom partials too.if this is still valid with provided templates in v14, please reopen a new issue with the information to reproduce the issue
I have no idea how to reproduce this bug. The form framework uses
property="{element.identifier}"in all templates.