[MAGNOLIA-6845] info.magnolia.cms.i18n.MessagesManager#DEFAULT_BASENAME points to messages file which doesn't exist Created: 26/Oct/16  Updated: 03/Nov/16  Resolved: 03/Nov/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5

Type: Bug Priority: Neutral
Reporter: Milan Divilek Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2016-10-26 at 13.45.38.png    
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
Epic Link: Phase out Admin-interface Legacy
Sprint: Basel 68
Story Points: 1

 Description   

info.magnolia.cms.i18n.MessagesManager is deprecated since 5.1.1, but it's still used (for example in info.magnolia.cms.security.auth.callback.FormClientCallback). And info.magnolia.cms.i18n.MessagesManager#DEFAULT_BASENAME point's to info.magnolia.ui.admincentral.messages_legacy which was removed in MGNLUI-4027.

So this can lead into missing i18n messages. For example in login form Screen Shot 2016-10-26 at 13.45.38.png.

We should remove usage of info.magnolia.cms.i18n.MessagesManager at all or at least change default_basename to point to existing file.


Generated at Mon Feb 12 04:18:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.