[CAMPMAN-29] CampaignReferenceResolverDefinition does not resolve the content in the correct language Created: 18/Oct/21  Updated: 02/Mar/22  Resolved: 01/Mar/22

Status: Closed
Project: Campaign Manager
Component/s: None
Affects Version/s: 3.1.5
Fix Version/s: 3.1.6

Type: Bug Priority: Major
Reporter: Tobias Kerschbaum Assignee: Raphael Falvo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File delivery_response_de.png     PNG File delivery_response_en.png     PNG File image-2021-10-18-15-30-08-541.png     PNG File image-2021-10-18-15-30-31-643.png    
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
[X]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:

 Description   

Steps to reproduce

  1.  Create a fallback Site configuration to be able to manage Campaigns in multiple languages
  2. Create a Fragment and manage two languages
  3. Add the Campaign to a page
  4. Resolve the Campaign with the resolver

Expected results

Like in normal components, the content should be served with the requested language:

Actual results

The content is served with all available languages:

Workaround

Development notes

The behavior can be reproduced in our Ecommerce-Headless demo. Ping me if you need to see it.



 Comments   
Comment by Raphael Falvo [ 01/Mar/22 ]

Checked on 3.1.6 without being able to reproduce the issue, has been already fixed.

http://localhost:8080/.rest/delivery/website?lang=en

http://localhost:8080/.rest/delivery/website?lang=en

 

 

Comment by Raphael Falvo [ 02/Mar/22 ]

Hello tobias.kerschbaum

Just FYI, I marked this one as closed, as I tested and the issue is not present anymore on 3.1.6, and also to get clarity on what is still open and what is not. In case this shall come back, we can just reopen it.

Generated at Sun Feb 11 23:55:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.