How to configure specific fields not to be translated?

Questions and Answers
1
System Information
  • Strapi Version: 3.6.2
  • Operating System: macOS Big Sur
  • Database: SQLite
  • Node Version: 14.15
  • NPM Version: 6.14.8
  • Yarn Version: 1.22.5

Hello, as I understand there seems no options to configure which fields could be translated or not.

I want to keep some specific fields, slugs for example identical for both locals.

2

Hi @lodisy

Can you list all the fields which can’t be translated or not ?

3

All fields can be translated by default. I did find options to configure. I thought the small icon was the toggler.

4

Typo *didn’t

5

When you edit your fields, in Advance Settings, you can find a checkbox to enable/disable localization, you can do it also manually in the content type json file at api folder. Unfortunately, right now it does not work with relationship fields.

1 Like
6

Thank you! I didn’t even find it before.

But unique fields like slug / sku must be localized? It would be weird for non-Latin locals.

7

Just uncheking the unique field, and generating random strings using lifecycle to avoid duplication should work.

8

Yeah, the slug field is also localized, it means you must put a slug for each localized page, it is because you are creating a new page for the same initial page (somehow linked) instead to add additional fields to the same page.