Freemarker ${i18n[..]} expressions shouldn't result in freemarker exception if
"i18nBasename" property is not set for paragraph
-------------------------------------------------------------------------------------------------------------------------------
Key: MGNLSTK-614
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-614
Project: Magnolia Standard Templating Kit
Issue Type: Improvement
Affects Versions: 1.2.1
Reporter: Vivian Steller
Assignee: Philipp Bärfuss
Calling ${i18n[....]} in a template that does not define i18nBasename throws a
freemarker exception "Expression i18n is undefined".
I suggest that the i18n array should always be defined in freemarker, no matter
what the i18nBasename is. Having no i18nBasename property in the paragraph
definition should IMO be handled as if the i18n messages file isn't available
and should not result in an exception.
So, this is most probably not a STK issue yet, however, I think it would make
sense to integrate something like ${i18n(...)} (method call, not array) into
STK to achieve the desired behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
