|
||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
To clarify this issue:
The problem is that the title property of the area will not be looked up in the message bundle specified by the i18nBasename from the area itself.
Instead, it will be resolved with the message bundle specified by its parent (the parent area or template definition).
I propose a change in info.magnolia.templating.elements.AreaElement. See attached patch (includes a test case).
The patched version will look for an i18nBasename on the area definition first, and it will fall back to the parent definition if there is none declared on the area.
I admit that this is a minor issue, but if the labels don't get resolved it always looks like there's something broken on the front end.
Also I believe that the new behaviour would be more consistent with how i18nBasename and label/description properties work on components.
Unfortunately I'm not quite sure how big the risk of breaking existing configurations would be.
Regards,
Andy