.svg?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp)
.png?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.png?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp){kind=icon}
Non-localizable
The Non-localizable property lets you set the field’s data only in the master language entry. This means it cannot be edited (or translated) in the localized copies of the entry.
The field data provided in the master language entry is automatically reflected in all localized copies of the entry. In localized entries, the field remains in a disabled (non-editable) mode.
Warning: If you edit the data of a Non-localizable field in the master-language entry and save the entry, the field data in all localized copies automatically updates, and the version number of the localized entries will increment by 1.
Note: In some cases, such as when you add a new instance of a Group, Modular Block, or Global in a localized entry, Non-localizable behavior may not apply. The new instance is treated as a localized addition, and its fields—including those marked Non-localizable—can be edited. For more details, refer to Managing Non-Localizable Fields.
For users on older plan, the following limitations apply:
- Fields inside a Modular Blocks field cannot be marked as Non-localizable
- Fields inside a Group and Global field marked as Multiple cannot be marked as Non-localizable
More articles in "Field Properties"
