Details
-
Improvement
-
Status: Open
-
Normal
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
The document type configuration in hippo:namespaces allows support for i18n on type and field definitions, but these are currently stored and managed on template type level, which cannot be reliably processed by the ContentTypeService (CMS-7024). Adding i18n support therefore will require improving or moving the current management of the i18n meta-data differently.
Attachments
Issue Links
- relates to
-
CMS-7024 Add a new readonly Content Type Service exposing the CMS Document types and repository Node types meta-data and constraints through a POJO bean model
-
- Closed
-