Closed supermoos closed 6 years ago
@supermoos could you create a reproduction of your code with a demo contentful account? 👍
I was setting it up, and the figured that contentful localizes assets too and that was what was causing the problem. I solved it by setting up a fallback locale in contentful so it serves up the default locales images. However this results in text strings also using fallback versions, which is not always what one may want. It would be a really nice feature if there was a way to request a fallback locale only for ContentfulAsset's but not sure if that's already possible somehow?
I have the same problem and I think it should load the default value if the field is not localised and the fallback is not set for the target language. Similar this fix #2937, so I think it is a bug, fields which are not media assets work as expected.
This still does not work for media assets I fear. I only get null
as the url for the non-localized images for any other language but the default (in my case en-US
)
I have this issue as well
Description
Looks like there is a bug in which all images assets are null, when using a different language than english:
Steps to reproduce
Here's my GraphQL Query:
Expected result
I should get the image source back for the language request on the pageHome.
Actual result
GraphQL result:
Environment
File contents (if changed)
gatsby-config.js
:package.json
:gatsby-node.js
: