Issue Bug Closed

#102138XLF files not working for finishers

Jakub Zgirski 10/10/23, 13:56 updated 12/02/25, 14:37

Description

We have a website that has the default DE language. We configure EXT:form, add the locallang.xlf and de.locallang.xlf files with translations for the finisher.
In my test i used EmailToReceiverFinisher and ConfirmationFinisher. For some reason both finishers use english translations (locallang.xlf) and when i remove EmailToReceiverFinisher from form definition then ConfirmationFinisher works like expected – it shows message from de.locallang.xlf.

Reviews 3

History 415

  1. Michael Reuber commented and changed PHP Version 8.1 8.2 <span data-processor="relativetime" data-value="2023-10-20T12:46:41+00:00" > 10/20/23, 12:46 </span>

    Jakub Zgirski wrote:
    > We have a website that has the default DE language. We configure EXT:form, add the locallang.xlf and de.locallang.xlf files with translations for the finisher.
    > In my test i used EmailToReceiverFinisher and ConfirmationFinisher. For some reason both finishers use english translations (locallang.xlf) and when i remove EmailToReceiverFinisher from form definition then ConfirmationFinisher works like expected – it shows message from de.locallang.xlf.

    I can confirm this behavior

  2. Nikita Hovratov commented <span data-processor="relativetime" data-value="2023-10-24T08:22:53+00:00" > 10/24/23, 08:22 </span>

    The documentation states that default behaviour should be the request language: https://docs.typo3.org/c/typo3/cms-form/main/en-us/I/Config/proto/finishersDefinition/finishers/EmailToReceiver.html#options-translation-language

    A security patch changed the default value to the “default language”: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68436

    I think this might be the issue, why finisher translations started to have the default translation language (english) in every language.

    Removing the entry:

          translation:
            language: Default

    restores the automatic behaviour. This is only possible through manual editing of the YAML though. I believe the select field needs another entry for “Auto”.

  3. Nikita Hovratov commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-03-28T10:10:08+00:00" > 03/28/25, 10:10 </span>

    Applied in changeset commit:bf0666040d9e0a6705c60235fd07c459ca480905.