[MGNLUI-4279] Properly support i18n on link field browse buttons Created: 15/Aug/17  Updated: 17/Jan/18  Resolved: 12/Oct/17

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5.7, 5.6

Type: Bug Priority: Neutral
Reporter: Cedric Reichenbach Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File LinkFieldProperties.png     PNG File labelessButton_selectOther.png    
Issue Links:
Relates
relates to CONTEDIT-143 Final content editor UI polish Closed
dependency
is depended upon by CONTEDIT-166 Remove FIXME statements from Stories ... Closed
relation
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Documentation update required:
Yes
Date of First Response:
Sprint: Kromeriz 111, Kromeriz 117
Story Points: 5

 Description   

Because LinkFieldFactory uses the deprecated #getMessage method for translating buttonSelectNewLabel, custom i18n messages are not picked up properly.

Currently, those labels are just hard-coded in English.

Possible workarounds

  • The high road: Fix LinkFieldFactory in UI and make it use a proper I18nizer
  • Workaround without touching UI: Use i18nBasename on individual fields to make our messages file visible to the legacy i18n mechanism

Generated at Mon Feb 12 09:15:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.