-
Notifications
You must be signed in to change notification settings - Fork 35
Entities and assets don't get linked when using multiple locales #95
Comments
Hey @frankmarineau, Looks like there is an issue with link resolution for localized content. I will look into it next week (I'm on vacation until Monday). In the meantime, you can solve the links locally by filtering in the views. Cheers |
Thanks a lot @dlitvakb! |
Hey there, I'm also currently facing this issue and try to filter the entries in the views but I'm having some trouble with fetching linked assets. I have a content_type named
How can I access the information of these linked Assets? I tried maybe fetching them locally by passing the following:
but that doesn't work. Any ideas about that? Thank you very much in advance! |
Hey @martzoukos, Sadly Assets are not regular entries, so they use a different API endpoint. I will try to get this solved between today and tomorrow, and release a new version with the fix early next week. Hope that helps |
Thank you very much @dlitvakb ! |
Fantastic. Thank you again David! |
@martzoukos no problem! new version Cheers |
Hey David, I'm still getting the same
response. |
Hey @martzoukos, are you using |
@dlitvakb I see that I'm using |
You can check by running |
Thanks, it outputs |
@martzoukos could you try again running like If the issue still persists, please open a Support ticket and share the details there? I'll be able to look in detail in your case, maybe I missed something on the fix. Cheers |
Tried running |
In app.contentful.com, please request to be assigned to me. |
Will do. Thanks! |
@dlitvakb I'm getting a slightly different problem here. Linked assets do now work, but not linked entries. |
@frankmarineau Looking into it early tomorrow. |
@frankmarineau new version of the Could you update and let me know if it works now? |
Issue is still persistent on assets that are localized (entries now work fine). Fix was found and currently adding specs around the feature. New version will be published within the next few hours or early tomorrow. |
Hey @frankmarineau @martzoukos, Version Please let me know if everything works for you now. Cheers |
Yes, it works! Thank you! |
If I add
locales: '*'
to the CDA query, assets and links will only show thesys
key and won't be populated with the actual linked resource. In the following example, I'm using two locales (en-us and fr-CA) and two content types: a Section that contains multiple _Topic_sHere's the generated yml I get for a Section if I don't specify multiple locales in the CDA query (
f.cda_query = {}
):💯 . The associated _Topic_s are populated.
Here is what I get when I set
f.cda_query = { locales: '*' }
:It loads plain fields just fine (the title), but linked entries are no longer populated.
For reference, here's what one of the Topic yml files looks like:
It's not shown in the above example, but the same issue happens with linked assets.
Additional information
master
)Any idea how to solve this? Thanks!
The text was updated successfully, but these errors were encountered: