Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.1.2
-
None
-
DX Core 6.2.16 limited to one site
Description
Steps to reproduce
- Define content type & content app with i18n properties.
- Define two sites (one more than licensed).
- Define fallback site with two locales for i18n.
- Try to edit content via content app.
- Use delivery API to access multilingual content.
.. Logs, screenshots, gifs...
Expected results
Fallback Site mechanism should still be working, i.e. multilingual editing of content should work. Multilingual API results should work.
Excess site should not be supported (and that should be signalled in the Site App).
Actual results
When editing content in a content app with i18n, no language selection is shown. No language specific field labels are shown.
When accessing multilingual page content via delivery API, only the default language is delivered, regardless of the language parameter.
Workaround
Delete the excess site definition.
Development notes
Checklists
Acceptance criteria