#109260Confirmation finisher language is wrongly connected to the preceding email finisher
Description
If a fixed language is set for an email finisher, the subsequent Confirmation finisher will also use this language.
finishers:
-
options:
subject: 'Message sent by contact form'
senderAddress: 'noreply@example.com'
senderName: '{name}'
attachUploads: true
recipients:
your.company@example.com: 'Your Company name'
addHtmlPart: true
## This value is passed on to the Confirmation finisher:
translation:
language: Default
identifier: EmailToReceiver
-
options:
message: 'Thank you for your message! We will get back to you as soon as possible.'
identifier: Confirmation
Expected behavior:
- The translation of the email finisher is only applied to this specific finisher.
- The language of the confirmation finisher depends on given translations in XLIFF (or form variants).
You have a request form in a multi-language website. All emails of this form are sent to the same email address.
- The sender should see a confirmation in the same language as the website and form.
- The mail recipient should receive all emails in their native language, regardless of the frontend language the sender used.
Reviews 1
History 5
-
Sebastian Klein commented <span data-processor="relativetime" data-value="2026-03-16T15:13:07+00:00" > 03/16/26, 15:13 </span>
-
Josua Vogel commented <span data-processor="relativetime" data-value="2026-03-16T22:17:37+00:00" > 03/16/26, 22:17 </span>
Hello Sebastian,
Thank you for reporting this bug. We fixed this bug in current main (v14): 91100: [BUGFIX] Prevent language inheritance in form finishers | https://review.typo3.org/c/Packages/TYPO3.CMS/+/91100
However, due to the complexity of the issue, we have decided not to create a backport.
I hope you understand.
-
Sebastian Klein commented <span data-processor="relativetime" data-value="2026-03-17T06:44:18+00:00" > 03/17/26, 06:44 </span>
Hello Josua,
I searched for existing issues, but must have missed this one. Good to know that it is already fixed for v14. The workaround works for me until the upgrade is performed.
Thank you for your work on the form improvements!This issue can be closed then.
-
Garvin Hicking changed status
NewClosed <span data-processor="relativetime" data-value="2026-03-17T06:44:35+00:00" > 03/17/26, 06:44 </span> -
Garvin Hicking changed Duplicates #101814 <span data-processor="relativetime" data-value="2026-03-17T06:45:10+00:00" > 03/17/26, 06:45 </span>
As a workaround, it is possible to unset the translation for the Confirmation finisher manually:
finishers: - options: subject: 'Message sent by contact form' senderAddress: 'noreply@example.com' senderName: '{name}' attachUploads: true recipients: your.company@example.com: 'Your Company name' addHtmlPart: true translation: language: Default identifier: EmailToReceiver - options: ## Unset to default behavior: translation: language: '' message: 'Thank you for your message! We will get back to you as soon as possible.' identifier: ConfirmationThe
translationoption is undocumented for the Confirmation finisher (possibly because you should not need it). It works, as this option is inherited from theAbstractFinisherclass.