[MGNLPUR-172] Components and dialogs relying on legacy i18n mechanism might not be translated properly because properties file might not be found (in time) Created: 18/Nov/16  Updated: 28/Nov/16  Resolved: 24/Nov/16

Status: Closed
Project: Magnolia Public User Registration
Component/s: None
Affects Version/s: 2.6
Fix Version/s: 2.6.1

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLPUR-164 Get rid of dependency to legacy admin... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: Basel 71
Story Points: 2

 Description   

The legacy messages_en.properties file was moved with MGNLPUR-164 making the translation unavailable for the legacy mechanism. We should move the file back to its original location until we have gotten rid of usages of the legacy i18n mechanism. This way we'll also be in-sync with the translations modules (which might be resolved correctly replacing the default translation with some fallback – via Locale.getDefault()).

The new mechanism is capable of falling back to the legacy one, but not vice versa.


Generated at Mon Feb 12 06:43:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.