[MGNLCTS-126] Support for complex fields Created: 11/Jan/21 Updated: 22/Sep/21 Resolved: 04/Feb/21 |
|
| Status: | Closed |
| Project: | Content Translation Support |
| Component/s: | None |
| Affects Version/s: | 2.5 |
| Fix Version/s: | 2.5.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Teresa Miyar | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 5 |
| Labels: | cs-bk, maintenance | ||
| 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
|
||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||
| Sprint: | Maintenance 42, Maintenance 43 | ||||||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||||||
| Description |
|
Add support for complex fields export/import, composite, switchable and multivalue For more information check: https://wiki.magnolia-cms.com/pages/viewpage.action?spaceKey=~tmiyar&title=Content+Translation+Support+Improvements |
| Comments |
| Comment by Riste Drangovski [ 11/Jan/21 ] |
| Comment by Riste Drangovski [ 25/Jan/21 ] |
|
How to test Issue: Steps to test:
note: we also need to check complex fields in combination of itemProvider and nameDecorator properties. |
| Comment by Riste Drangovski [ 29/Jan/21 ] |
|
mdrapela Could you please add the following to the Release Notes? It was necessary to break binary compatibility at from: this is needed because for one multi field we can get multiple translation items. |
| Comment by Tomáš Gregovský [ 04/Feb/21 ] |
|
hero.yaml
|
| Comment by Riste Drangovski [ 04/Feb/21 ] |
|
As far as I can see the issue is related with the itemProvider configuration. I short: A bit longer: Please check screenshots and attached yaml configuration ... I'm not sure that this is translation related issue, pls let me know if we should do anything about this. |
| Comment by Federico Grilli [ 04/Feb/21 ] |
|
rdrangovski indeed removing itemProvider configuration from composite field seems to do the trick. We could create a follow-up issue to investigate this further in order not to delay 2.5.1 release. tgregovsky WDYT? |
| Comment by Tomáš Gregovský [ 05/Feb/21 ] |
|
hi rdrangovski and fgrilli, yes removing item provider from composite field helps, so this is fine for our project. would would agree on follow up ticket, since using itemProvider for composite field is documentation https://docs.magnolia-cms.com/product-docs/Templating/Dialog-definition/Field-definition/List-of-fields/Composite-field.html |