Details
-
Sub-task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Saigon 151
Description
Composite models:
Setting i18n to true on a CompositeField is irrelevant (should have no effect); set it on the sub-field(s) instead.
Given the model below, let's consider two use cases for composite groups:
model:
properties:
- "name"
- "position"
type: Job
subModels:
"Job":
properties:
- "title"
- "organization"
A. Enable `i18n` on the position property
* mika
- name: Mika
* position_fr
- title: Ingénieur Logiciel
- organization: Magnolia International # assuming we don't really translate organization name, but here we could
* position_hr
- title: Softverski Inženjer
- organization: Magnolia International
B. Enable `i18n` on the title property
* mika
- name: Mika
* position
- title_fr: Ingénieur Logiciel
- title_hr: Softverski Inženjer
- organization: Magnolia International # common for all languages here
Multivalue properties:
since
MGNLUI-3169, we support both use cases:
- i18n set to true on a MultiField: stores a different set of entries per locale. No need to enable i18n on sub-fields (would be redundant).
- i18n set to false on a MultiField: stores a single set of entries. Entries may be translated 1-to-1 by setting i18n to true on sub-fields.
See also MGNLUI-3610, MGNLUI-3633