Details
-
Improvement
-
Resolution: Not an issue
-
Neutral
-
None
-
None
-
None
-
None
Description
@kareldewitte: is https://documentation.magnolia-cms.com/display/DOCS/Making+a+module+translatable documentation about using i18n in template script complete? I have not got this working yet since I get error message that i18n is null or missing(freemarker.core.InvalidReferenceException). Discussion at https://jira.magnolia-cms.com/browse/MAGNOLIA-5876 suggest that i18nBasename should be also set up. Then again looking at https://documentation.magnolia-cms.com/display/DOCS/Template+definition seems like since I have mgnl-i18n inside modules resource folder I should be fine.
I have tried with and without basename and even if I have not got the configuration right I should be missing key, but not i18n itself. (edited)
well I found from https://documentation.magnolia-cms.com/display/DOCS/New+and+old+i18n+API in fine print that new API does not work for UI translations in resource bundles. Or "template labels" - as you in Magnolia call them.
I think it would have saved some time if there had been something mentioned about it in https://documentation.magnolia-cms.com/display/DOCS/Making+a+module+translatable#Makingamoduletranslatable-Templatescript and https://documentation.magnolia-cms.com/display/DOCS/Template+definition#Templatedefinition-Templatedefinitiontypes