-
Bug
-
Resolution: Fixed
-
Critical
-
5.1
-
None
-
None
-
-
Empty show more show less
-
5.1 - Final
When trying to put the new i18n system in place for the workflow module I realised that many keys I expected the system to generate weren't actually generated, for example the keys for save and cancel buttons are never created or the field labels in forms and dialogs. After some investigation, it turned out that forms and dialogs haven't been properly decorated, i.e. the calls to I18nizer.decorate() are either missing or put in the wrong place. After putting them in the right spots so that the whole object hierarchy is properly decorated, the AbstractFormKeyGenerator has started failing with some NPE which need to be fixed. Furthermore, we miss a KeyGenerator for FieldValidatorDefinition(s). The reason why everything apparently works now, i.e. most stuff is basically translated is because translations are currently hardcoded in configuration but once we clean config up and remove labels, descriptions and other i18n properties then the problem would become apparent.
- is cloned by
-
MGNLUI-2195 i18n - Forms and dialogs are not properly decorated
- Closed
- is related to
-
MAGNOLIA-5332 AbstractI18nKeyGenerator could expose method to get id or name of unknown i18n root object
- Closed