[MGNLUI-7022] i18n for switchableField doesn't do fallback Created: 20/Jan/22 Updated: 22/Feb/23 Resolved: 15/Nov/22 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Tomáš Gregovský | Assignee: | Unassigned |
| Resolution: | Resolved | Votes: | 2 |
| Labels: | i18n | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| 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: | jcrChildNodeProvider creates nodes for unselected subforms | ||||||||
| Story Points: | 3 | ||||||||
| Team: | |||||||||
| Description |
| Comments |
| Comment by Michael Schneider [ 24/Aug/22 ] |
|
Additional input: This bug also includes the link targets in our components. In the default English version, it looks fine. If there are no link targets picked in the other languages, it took the default EN targets. But that is not the case anymore and super annoying:
Example: EN
DE - German
--> Not link buttons in the Hero component are being displayed in the DE version
EN
DE
|
| Comment by Michael Schneider [ 04/Oct/22 ] |
|
As discussed with dmaslanka https://www.loom.com/share/dcda56895d6e44a8af6821f3dfa7559e About the blocker scale, I would say it's a solid 8, since I need to manually add those links in not just one but in total of six languages, with is super annoying. |
| Comment by Adam Siska [ 04/Oct/22 ] |
|
Since 6.2.14 (MGNLUI-6905) only subnodes for selected languages are created. Does it make the issue obsolete then? Or should we investigate more the use case even for one selected and not used/filled language variant? |
| Comment by Michael Schneider [ 04/Oct/22 ] |
|
HI asiska , for me, the following use case would be best:
I cannot keep the current state where I need to fill out the same dialog field up to 4-6x because the regional language dialog field is empty and therefore the asset or the link is not being displayed (doesn´t take on the default languages English if empty) Thanks |
| Comment by Adam Siska [ 07/Oct/22 ] |
|
Discovery
There should be possible ad hoc workarounds:
|
| Comment by Adam Siska [ 18/Oct/22 ] |
|
This issue is superseded and would be fixed by |
| Comment by Dominik Maslanka [ 15/Nov/22 ] |
|
Closing this issue as the problem gets resolved with |