Bug #79551
closed
Takes care of localization of tt_content_defValues
Added by Eric Chavaillaz almost 8 years ago.
Updated about 7 years ago.
Description
Hi,
If I set a tt_content_defValues
in the TypoScript configuration with a value localizable, the controller of the new content elements do not take care of it.
Thanks
- Status changed from New to Under Review
To answer Tymoteusz on Gerrit, an example of use case.
If I set this in my TypoScript configuration something like this:
mod.wizards.newContentElement.wizardItems.plugins.elements.plugins_tx_myext_pi1 {
iconIdentifier = content-plugin-myext-pi1
title = LLL:EXT:myext/Resources/Private/Language/locallang_pi.xlf:pi_wizard_title
description = LLL:EXT:myext/Resources/Private/Language/locallang_pi.xlf:pi_wizard_description
tt_content_defValues {
CType = list
header = LLL:EXT:myext/Resources/Private/Language/locallang_pi.xlf:pi_wizard_title
list_type = myext_pi1
}
}
The value of the title is localized, so the behaviour is fine, but the default value for the header
will not be translated (the value will be LLL:EXT:myext/Resources/Private/Language/locallang_pi.xlf:pi_wizard_title)
So the patch fix this case. I don't think it is really a feature, but if you consider like this, I can change my patch.
Thanks
- Target version changed from 8.6 to 8 LTS
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF