[MGNLREST-318] Rest Calls To Nested Multivalue Composite Fields Return Empty Created: 09/Jul/21  Updated: 22/Sep/21  Resolved: 25/Aug/21

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: 2.2.8
Fix Version/s: 2.2.9

Type: Bug Priority: Blocker
Reporter: Julian Nodarse Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: cs-bk, headless-team-support, maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File restcall_lang_all.png     PNG File restcall_lang_de.png    
Issue Links:
Problem/Incident
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Sprint: HL & LD 35, HL & LD 36
Story Points: 5

 Description   

Using the delivery endpoint with nested multi composite fields and i18n returns empty lists.

The rest endpoint logic that is used to pick up the proper i18n values from the JCR when specifying a language filter in the rest call is looking for the wrong node names. As a result, an empty list is returned with the call although there are items with i18n in the JCR.  

When using the “all” lang parameter, the node will be returned as <nodename>_<language> i.e “testnode_de” but when you specify a language such as lang=de , then the parent node gets seen as <nodename> i.e. “testnode”, so it does not detect any of the other language’s child nodes from the parent. 

Please see screenshot for rest results.

 



 Comments   
Comment by Lukasz Skolarus [ 04/Aug/21 ]

What is status of this ticket ? Is someone working on it ?

Comment by Simon Lutz [ 05/Aug/21 ]

lskolarus We're validating if the previous issue MGNLREST-286 fixed with Magnolia 6.2.9 is solving this issue. Your colleagues are doing an update to a later Magnolia version, please have a look at the support ticket.

Comment by Leah Staniorski [ 10/Aug/21 ]

https://www.dropbox.com/s/9kdxw6qz1i4d1du/Paulina%20Jagielka%20-%20Magnolia%20Call%20for%20export_import%20issues%20%26%20page%20links%20case-20210806_143454-Meeting%20Recording.mp4?dl=0

This issue begins at 2:50 minute time mark.

Generated at Mon Feb 12 06:58:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.