Issue Bug Closed

#98254Subject inferred from option not localized in form finisher

Philipp Holzmann 09/03/22, 07:47 updated 11/06/26, 08:08

Description

The Subject of the Tx_Form’s Finisher can be translate, but not if it’s an option of a select field.

For a workaround, we added this to the translationChain in translateFinisherOption of the TranslationService

foreach ($translationFiles as $translationFile) {
            if (!empty($originalFormIdentifier)) {
                $translationKeyChain[] = sprintf('%s:%s.finisher.%s.%s', $translationFile, $originalFormIdentifier, $finisherIdentifier, $optionKey);
            }
            $translationKeyChain[] = sprintf('%s:%s.finisher.%s.%s', $translationFile, $formRuntime->getIdentifier(), $finisherIdentifier, $optionKey);
            //added with option value by INDIZ
            $translationKeyChain[] = sprintf('%s:%s.finisher.%s.%s.%s', $translationFile, $formRuntime->getIdentifier(), $finisherIdentifier, $optionKey,$optionValue);
            //end of changes...
            $translationKeyChain[] = sprintf('%s:finisher.%s.%s', $translationFile, $finisherIdentifier, $optionKey);
        }

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 4

  1. Oliver Hader changed subject Tx_Form Subject Subject inferred from option not localized in form finisher <span data-processor="relativetime" data-value="2022-09-05T09:51:05+00:00" > 09/05/22, 09:51 </span>

  2. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-06T08:08:20+00:00" > 11/06/26, 08:08 </span>

    Fixed with #106903 (main, 14.3): the email finisher now resolves {elementIdentifier} in subject, title, message and sender name to the translated label of the selected option instead of the submitted option key. The confirmation and flash message finishers do the same. Custom finishers can use parseOptionAsDisplayValue() for the same behaviour.