Keith Hon
Keith Hon
I can reproduce on windows 10 and made a patch to fix the error on strapi 4.3.4 [@strapi+typescript-utils+4.3.4.zip](https://github.com/strapi/strapi/files/9348202/%40strapi%2Btypescript-utils%2B4.3.4.zip)
Is not being able to reference a relationship entity from a different locale an intented bahaviour? If it's a an issue, is it related to [Field localization](https://github.com/strapi/strapi/issues/12538) ?
> > Is not being able to reference a relationship entity from a different locale an intented bahaviour? If it's a an issue, is it related to [Field localization](https://github.com/strapi/strapi/issues/12538) ?...
Hopefully they are going to address this. A current workdaround is to add localized field to the collection type. e.g. name_en, name_de to avoid using 18n at all.
> > Hopefully they are going to address this. A current workdaround is to add localized field to the collection type. e.g. name_en, name_de to avoid using 18n at all....
I agree that Gatsby is slow for development. But how about using nextjs with typescript? IMO, it's better to use 1 framework across the admin and storefront apps.
Hi @Sukriti-sood @olivermrbl any updates on this?
Is it possible to have localized names for each product? And the shoppers could switch the site's language
I experience the same issue with nextjs
i published my own ssr version at https://www.npmjs.com/package/@moredeal/react-slick/