Tracking Issue - Field localization

[derrickmehaffy]

This issue has been created as a global tracking issue regarding certain fields that are not handled by the i18n localization properly.

This tracking issue is for

• Fields that aren't being localized properly
• Fields that shouldn't be localized (or have the option not to)
• Errors thrown localizing certain fields
• Unique errors with localization

Related issues (more will either be added here or in the comments):

• Unique fields must be localized error for Integer type field #12436 ✅
• Unique and localisation - checks in all languages #12248 ✅
• UID field can't remain the same when using i18n #10107 ✅
• Not able to set slug with internationalization feature - Not unique #10169 ✅
• Unique localized fields are impossible with different UTF-8 characters #10694 ✅
• Unable to disable localization for relationship fields. #10322 ✅

Before this issue can be closed all of the parent issues must be fixed, fixed issues will be marked with a ✅

[SalahAdDin]

Isn't possible to ignore relational fields on localization yet? it is very important, not all relational fields need to be localized, it would be possible, at least on the json configuration file, to ignore localization when we need it.

[EarMaster]

I can only quote @terion-name

@sam-pires are there any plans to rework entire i18n model? absence of parent id of an entity with localizations is a huge pain, including in realm of relations. You relate entities, not localizations. If I have a localized post that has an author - author is one for entire post, not for a locale. If I have an event with translations, registration for an event is to event entity, not to a locale, etc
Entire datamodel of i18n is flawed

This is still true.

[SalahAdDin]

I can only quote @terion-name

@sam-pires are there any plans to rework entire i18n model? absence of parent id of an entity with localizations is a huge pain, including in realm of relations. You relate entities, not localizations. If I have a localized post that has an author - author is one for entire post, not for a locale. If I have an event with translations, registration for an event is to event entity, not to a locale, etc
Entire datamodel of i18n is flawed

This is still true.

Yeah, this is totally true!!!

[Keith-Hon]

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 ?

[SalahAdDin]

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 ?

It is not certain, at least for me.

It seems there is no further work on the related issues.

[EarMaster]

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 ?

It may not be intended but it is a result of the design of the i18n model. Seperate locales are seens as different entities only which are only linked together. This means that there is no way of referencing an entity which does not exist in your current locale. This is - in my opinion - a strange but also fatal flaw of the i18n implementation used by strapi.

[SalahAdDin]

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 ?

It may not be intended but it is a result of the design of the i18n model. Seperate locales are seens as different entities only which are only linked together. This means that there is no way of referencing an entity which does not exist in your current locale. This is - in my opinion - a strange but also fatal flaw of the i18n implementation used by strapi.

A big one, this is very easy in other CMS like Wagtail.