[MGNLUI-2087] Untranslated old keys due to not passed i18n bundle basename Created: 13/Sep/13  Updated: 03/Oct/13  Resolved: 17/Sep/13

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

Type: Bug Priority: Major
Reporter: Christoph Meier Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File delete-action-missing-translation-2.png     PNG File delete-action-missing-translation.png     PNG File not-translated-key.png     PNG File not-translated-key3.png     PNG File not-translated-key4.png     PNG File not-translated-key_2.png    
Issue Links:
dependency
is depended upon by MGNLUI-1826 i18n keys: As a developer I don’t hav... 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
Date of First Response:
Sprint: 5.1 Beta1- Frontend, 5.1 - Final

 Description   

Not translated (old) keys / due to not base i18n-bundlebase-nam, i.e. "field.link.select.new"

There are already many places in the in the code where "info.magnolia.ui.admincentral.messages" has been added as a parameter (which was not necessary in the old system as MessagesManager used to point to "info.magnolia.ui.admincentral.messages" whereas now it points to "info.magnolia.ui.admincentral.messages_legacy").



 Comments   
Comment by Christoph Meier [ 13/Sep/13 ]

found on pages , categories , ...

Comment by Christoph Meier [ 13/Sep/13 ]

in some cases, i guess, we MUST have the above described requirement.
e.g. in DeleteActionDefinition it seems NOT possible to set the "info.magnolia.ui.admincentral.messages" as basename
(at least i was not able to do ... )

Comment by Federico Grilli [ 17/Sep/13 ]

This is more of a workaround than a proper solution, the idea being that the new 1i18n system should be able to deal with such keys in a more elegant way.

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