Relation between localized and not localized content type

System Information
  • Strapi Version: v4.12.1
  • Operating System: MacOS
  • Database: MariaDB
  • Node Version: v18.17.0
  • Yarn Version: v3.6.1

Hello there, I am having problems with the relation between a content type that has internacionalization activated and a content type that does not have internacionalization activated.

If I have content type A that has localization, and content type B that does not have localization. When I try to create an entry in the content type B, I want to relate it to an entry in the content type A.

But the dropdown that shows the entries of the content type A, only show the entries of the default locale.
So I can only relate the content type B with the entries of the content type A that have the default locale. The other locales are not showing up.

Does anyone knows a good workaround for that?


At the moment, my solution is to never work with the relation starting from the non-localized content type.

So the direction of the relation should always be from the localized content type to the non-localized content type, or of course, just not localize both or localize both.

In some cases, I found that turning off the internationalization for one content type made the direction of the relation always be from the localized to the non-localized in my data structure. So it was more of a content type design problem in my case.

1 Like