Bug #67005
closed
$instance->localeDependencies is not filled properly in FLUIDTEAMPLATE
0%
Description
If you use f:translate in an FLUIDTEMPLATE outside an extension with no extension and/or plugin set it will always return the default translation.
The bug has to be somewhere in Locales.php:170 where the localeDependencies array is filled. It will only be filled with 5 char language codes but most of them are two char codes...
HOTFIX:
Dont use the full path to an extension language file like:
LLL:EXT:dbay_loginbox/Resources/Private/Language/locallang.xml:Login.usernameLabel
Set the extension in the typoscript for the FLUIDTEMPLATE:
10 = FLUIDTEMPLATE
10.extbase.pluginName = OverlayLoginbox
10.extbase.controllerExtensionName = DbayLoginbox
and then the following translation key will be translated correctly:
Login.usernameLabel
But now we only can use one extension language files in our FLUIDTEMPLATE
Updated by
Updated by Claus Due about 9 years ago
- Category changed from Fluid to TypoScript
- Complexity set to easy
I'm moving this one to the "TypoScript" categories for the following reasons:
- Fluid itself does only what it is told by configuration and the source of the problem is in this (default) configuration.
- Fluid only delegates translation to the core - it does not do any actual translating or resolving of active language.
- It could be seen as related to translation, but I expect a solution can be found in TypoScript (default controller/package perhaps).
- The change needs to be performed in the TypoScript object rendering instructions and mapped to Request properties.
NB: supports 100% same API in standalone Fluid and TYPO3 Fluid so don't worry about that part ;)
Complexity set to "easy" but may be a nobrainer.
Updated by Benni Mack over 4 years ago
- Related to Bug #69125: language_alt only works for pibase and extbase plugins added
Updated by Christian Kuhn almost 2 years ago
- Status changed from New to Closed
Hey. I hope it's ok to close here: The issue is quite old and got an answer from Claus without further reaction. In case this is still an issue, please feel free to open a fresh issue with more information.