[MULTISITE-114] Fallback Site i18n not working for Content Apps when number of sites is exceeded Created: 16/Feb/22  Updated: 16/Feb/22

Status: Open
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: 2.1.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Henning Rietz Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

DX Core 6.2.16 limited to one site


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled

 Description   

Steps to reproduce

  1. Define content type & content app with i18n properties.
  2. Define two sites (one more than licensed).
  3. Define fallback site with two locales for i18n.
  4. Try to edit content via content app.
  5. 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


Generated at Mon Feb 12 06:06:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.