Hello! I'm building a multi language website with Prismic and Gatsby. I'm having trouble with fetching the data in my default language when first loading the page. I get one of the alternative locales, and not always the same. Sometimes I suspect it changes when I have published something. Now I h…

Hello, @happyatwork team. I think this could happen because the createPages method is designed to create pages from components programmatically but in the /templates directory rather than the /pages one. This seems like a probable reason why this odd behaviour happens in the routes; as explained in…

Hello, thanks for reaching out and for joining the community! This is very odd because the API response always retrieves the master language and only brings the other ones if you specifically query your documents by language. I can see that you're already doing that by using dynamic variables. It …

Thanks for your answer. I'm using gatsby-node, createPages and a link resolver: exports.createPages = async ({ graphql, actions }) => { const { createPage } = actions const pages = await graphql(`{ allPrismicLanding { nodes { url type …

Do you have any suggestions how to solve this? We are a growing company and this issue is creating problems on search engines, on online advertising and so on. We will unfortunately have to consider changing our CMS if this problem persists.

Master locale not queried by default

Developing with Prismic

Topic		Replies	Views
Prismic returns different language first (not master locale) Developing with Prismic graphql	6	1686	May 25, 2021
Multilangual Gatsby Developing with Prismic gatsby	9	690	November 4, 2021
Bug: GraphQL API not returning documents in every locales Developing with Prismic graphql	3	1105	October 29, 2020
Example multilanguage Gatsby4 and Prismic Developing with Prismic gatsby	7	600	April 5, 2023
GRaphQL not returning all languages Developing with Prismic graphql	2	1030	December 7, 2020

Master locale not queried by default

Related topics