[MGNLUI-4450] Multivalue composite language dependent fields are not displayed when we "add" a new one in a different language than the default Created: 06/Jun/18 Updated: 05/Aug/21 Resolved: 21/Jul/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | dialogs |
| Affects Version/s: | 5.4.15, 5.5.10, 5.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Viet Nguyen | Assignee: | Mikaël Geljić |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | maintenance, tech-debt | ||
| Remaining Estimate: | 0.5h | ||
| Time Spent: | 1h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| 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: | |||||
| Epic Link: | Support | ||||
| Description |
|
Please reference to original ticket SUPPORT-8744 for more information.
Expected result: |
| Comments |
| Comment by Mikaël Geljić [ 07/Jun/18 ] |
|
viet.nguyen turn i18n to false on the MultiValueFieldDefinition. Setting it to true there means that you want a different set of entries per language. |
| Comment by Viet Nguyen [ 08/Jun/18 ] |
|
Hello mgeljic,
--> This's not what this issue mean. The issue is switching back and forth between different languages made the fields disappear on UI. Please try my reproduce steps to get an insight. This is an issue but not a major one, but closing it as not an issue sound not very logical. Also
--> I would say 'no', otherwise please update our i18n documentation, setting i18n to true means customers would like to have multiple languages on the same data set. Hope this helps! |
| Comment by Mikaël Geljić [ 08/Jun/18 ] |
|
Hey viet.nguyen, I did take your steps. Behavior before closing the dialog (4) vs. after reopening it (5) is consistent. The i18n setting is not inherited by sub-fields; the proper way is to use it just for the literal text fields where you expect to have translations. Actually, I found another issue with the definition: the name property is also i18n'ed. This is used by the save action for the JCR node name, and our i18n doesn't operate over different nodes. Still this might confuse the transformer while switching languages. Once turned off, the fields stay on screen as expected (4).
It's not about interpretation here, I'm telling you how it works. That said, I agree with you that Multivalue field documentation lacks a note about this. Feel free to file a DOCU ticket. |
| Comment by Viet Nguyen [ 11/Jun/18 ] |
|
First of all I've turn i18n on Multi value field to false and change a sub label to 'Select a segment 2' to make sure that the new setting get affected. |
| Comment by Mikaël Geljić [ 23/Aug/18 ] |
|
With i18n = false: same set, same count of entries With i18n = true: different set, different count of entries (since you say "because we have more promotions in DE than EN") In both cases, I could not reproduce any error, missing field, nor misbehavior. Mind that if the proper configuration to achieve the desired behavior produces a different structure to that of existing data, you have to upgrade your content accordingly (best via groovy script). I'm attaching the definition as well MGNLUI-4450-multifield-i18n.yaml |