You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In contentful, you may have multiple locales but only certain fields of certain content types may be localized. This is not properly supported for entries with only certain localized fields as described in #4169 (also related to #4168).
Example
I have a content type Navigation that has a non-localized field links which holds many references to entries of content type Link. A Link has a localized title field. A gatsby node for a localized Link should have a (reverse?) linkage to its parent Navigation node in the default locale but instead links to the completely empty localized node.
Problem description
I have now found out that entries of a content type which has no localized fields at all are also not supported correctly. Before creating linkages (and probably reverse linkages too), it is checked if the id is resolvable, but then the link does not point to the id, but to the localized id, whether there is a localized version of the linked entry or not. So far this has not been a huge problem because at least the completely empty localized node existed and could be linked to. In my PR #4517 I am working on omitting completely empty localized nodes, because they cause problems (#4170). When these nodes are filtered out, linking to these non-existing nodes cause a TypeError.
The text was updated successfully, but these errors were encountered:
I discovered this during my work on #4517 (comment).
Context
In contentful, you may have multiple locales but only certain fields of certain content types may be localized. This is not properly supported for entries with only certain localized fields as described in #4169 (also related to #4168).
Example
I have a content type
Navigation
that has a non-localized fieldlinks
which holds many references to entries of content typeLink
. ALink
has a localizedtitle
field. A gatsby node for a localizedLink
should have a (reverse?) linkage to its parentNavigation
node in the default locale but instead links to the completely empty localized node.Problem description
I have now found out that entries of a content type which has no localized fields at all are also not supported correctly. Before creating linkages (and probably reverse linkages too), it is checked if the id is resolvable, but then the link does not point to the id, but to the localized id, whether there is a localized version of the linked entry or not. So far this has not been a huge problem because at least the completely empty localized node existed and could be linked to. In my PR #4517 I am working on omitting completely empty localized nodes, because they cause problems (#4170). When these nodes are filtered out, linking to these non-existing nodes cause a TypeError.
The text was updated successfully, but these errors were encountered: