[MAGNOLIA-1524] AdminTreeConfiguration should be i18n aware Created: 10/May/07  Updated: 23/Jan/13  Resolved: 10/May/07

Status: Closed
Project: Magnolia
Component/s: admininterface, core
Affects Version/s: None
Fix Version/s: 3.1 M2

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1525 Lists should be i18n aware Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

Currently, AdminTreeConfiguration implementations have to get their own Messages bundles: the various setLabel methods on menu items are expected to be called with pre-translated messages. If trees had a configurable i18nBasename property like other controls, they could be customized easily without touching code.



 Comments   
Comment by Magnolia International [ 10/May/07 ]

done.
trees can now have a i18nBasename property in their config, which denotes the message bundle that their respective AdminTreeConfiguration instance will get when setMessages is called by the tree handler.
this message bundle is chained with the default admininterface messages bundle.
see dms or forum modules for an example.

Generated at Mon Feb 12 03:27:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.