Partially wrong language when fetching content from Content Delivery API

[alekos-captureone]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.5.2

Bug summary

While fetching content from Content Delivery API, some parts of it are in the wrong language.

We recently migrated from v8 to v13 and we used to have nested content. After communication with support agents we migrated all our nested content into block lists but the problem still persists.

We also see this behaviour:

• When we Save and Publish a page (or when we clear the Memory Cache), then the first language that gets fetched is correct.
• When we fetch another language, then some parts are in the language the got fetched first.

Specifics

We can give you access to the project if you need to look into the backoffice

https://dev-capture-one-cms.euwest01.umbraco.io/umbraco/delivery/api/v2/content/item/de?expand=properties[$all]&take=1000

Steps to reproduce

1. Save and publish a page
2. Fetch this pages content in a language (eg. Japanese)
3. Fetch again this page in another language. Some parts will be in the language that was first fetched (Japanese in this case)

Expected result / actual result

No response

[github-actions[bot]]

Hi there @alekos-captureone!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:

[kjac]

Hi @alekos-captureone,

Thanks for reaching out. Would I be correct in assuming you're using Nested Content for the buttons?

[alekos-captureone]

Hi @kjac, it was migrated from nested content to block list (as with all our content in the Dev environment).

[kjac]

Thanks @alekos-captureone 😄 I'll try to reproduce it

[alekos-captureone]

Thanks @kjac, I can also give you access to the environment if you want to check further.

[kjac]

Hi again @alekos-captureone. Sorry for the belated response, we've been rather busy with the V15 release.

I can't really reproduce this on V13. Here's my test content:

It's a block list with a nested block list. The nested block contains an URL Picker. The picked content is language variant and published in both English and Danish.

When fetching the English language variant:

...the resulting output contains the English version of the content picked in the URL Picker:

Similarly when fetching the Danish language variant:

...the resulting output contains the Danish version:

[alekos-captureone]

I see... Is there a way to see it in our own implementation and try to identify what is wrong and why we are getting this behaviour?

[kjac]

I would try invoking the endpoints from Swagger. Maybe use the "by ID" endpoint to root out any routing confusion. And remember to include the accept-language header.

Also - are we doing the same thing? Read: Is my test setup identical to yours (albeit a boiled down version)?

[alekos-captureone]

The setup looks the same, yes.

You can try GETting these endpoints:

First try German (you can also try it with the Accept-Language header) https://dev-capture-one-cms.euwest01.umbraco.io/umbraco/delivery/api/v2/content/item/de\?expand\=properties\[$all\]\&take\=1000

Then in English you should see the buttons (search for a "buttons" node) in german (both the names and the links will start with /de): https://dev-capture-one-cms.euwest01.umbraco.io/umbraco/delivery/api/v2/content/item/en\?expand\=properties\[$all\]\&take\=1000

[kjac]

@alekos-captureone I think the best approach here is to reproduce the setup in a simplified local version. If the problem still persist I'd be very interested in the resulting database. If the problem does not persist, perhaps you'll be able to figure out what differs between the dev environment and the simplified local version?

[alekos-captureone]

Unfortunately we are unable to identify what is different... It would be great if someone could have a look to our implementation and help us with what is wrong and we get mixed languages...