[MAGNOLIA-6920] i18n message keys - cross module interference Created: 11/Jan/17 Updated: 11/Jan/17 Resolved: 11/Jan/17 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | 5.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Workaround exists | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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
|
| Description |
|
I have the MTK module installed. The message keys found in that module are being applied to the dialogs of my custom module. I have a training light module (attached) with two dialogs. The page properties dialog is showing a help tip that comes from MTK. The textImage dialog has a form label being applied that I cannot seem to override. The bug is that the name of the definition file does not seem to have any affect or create a distinction. MTK defines the property as basic.title.description. That should not impact the label pageProperties.title.description. |
| Comments |
| Comment by Richard Gange [ 11/Jan/17 ] |
|
I am able to workaround the issue using a properties file with more specific keys. This key from magnolia-templating-kit-messages_en.properties # tabMain ... ... basic.title.description=Title of the page. is setting the description property on the title field of the page properties dialog. This happens when I don't set anything explicitly. I am able to "override" the label with a local one in the definition file (single language). Or I can create my own properties file which declares a more specific key like tabMain.title.description. Or, perhaps, with a proper descriptor file I could get the layering correct. |