Sign in Register
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • jcrmerlin 3 posts 73 karma points
    1 week ago
    jcrmerlin
    0

    Content Delivery API with multi culture

    Hi all,

    I noticed a strange behavior when requesting content using the Content Delivery API.

    I have a Document Type A with two cultures, 'en-US' (which is the default in my case) and another (not important, let's assume 'es')

    Then I create content for Document Type A, let's call it Welcome. I add all the translations for both languages.

    At this point, if I request the item through the Content Delivery API and Accept-Language 'es', I get a 404.

    Now, if I go back to Welcome and add the hostnames for cultures (let's assume '/en-US/welcome' and '/es/bienvenido') and then request the content through the Content Delivery API, then I get the content properly.

    Is that an expected behavior? I'm planning on using Umbraco headless, and it seems like a configuration not actually needed for that purpose (or maybe I'm missing something)

    Thanks!

    Copy Link
  • jcrmerlin 3 posts 73 karma points
    1 week ago
    jcrmerlin
    0

    I forgot to mention that I'm filtering the items by path.

    In my example, I have a root page called 'Shop' and then 'Products' below it. So I'm making this call:

    await UmbracoContentService.GetContentAsync( skip: 0, take: 100, startItem: "shop", filter: ["contentType:product"], sort: ["name:asc"], expand: "all", preview: false, acceptLanguage: SelectedCulture );

    Where SelectedCulture is 'en-US' everything is fine, when I switch to 'es' nothing is returned unless culture and hostnames is configured.

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft