TYPO3 Core

Hello Benni,

in Core we have currently following line in ImageManipulationElement.html:

<f:translate id="{cropVariant.title}" default="{cropVariant.title}" />

And yes, this line sometimes throws an Exception. I'm currently not really know why. Here is an idea:

If f:translate was called the first time it will generate hundreds of compile rows in Cache FluidTemplates:

        return sprintf(
            '\\%1$s::translate(%2$s[\'key\'] ?? %2$s[\'id\'], %2$s[\'extensionName\'] ?? $renderingContext->getControllerContext()->getRequest()->getControllerExtensionName(), %2$s[\'arguments\'], %2$s[\'languageKey\'], %2$s[\'alternativeLanguageKeys\']) ?? %2$s[\'default\'] ?? %3$s()',
            LocalizationUtility::class,
            $argumentsName,
            $closureName
        );

and after that, the render() method will be called. There you will find a try-section which will catch the \InvalidArgumentException, if $extensionName was not given and default $value will be set to {cropVariant.title}.

With next request the compiled FluidTemplate will be called, which you (Core) have drastically changed with the last commits. This compiled FluidTemplate will only call LocalizationUtility::translate(). There is no catch against \InvalidArgumentException anymore. So maybe method compile should create a better compile Template or we can return back to renderStatic as in previous versions.

Nice greetings

Stefan

Ok...confirmed. On first request render() will be called which catches the Exceptions and at second request the compiled version will be called, which does not catch the Exception and can not handle default values.

IMHO f:translate has to be repaired.

Stefan