Issue Bug Closed

#87121Content fallback does not work, when page translation does not exist yet

Helmut Hummel 12/11/18, 10:46 updated 12/12/18, 08:37

Description

Given content fallback is configured
And a page “foo” exists only in default language English, but not in translation to Danish
I would expect that generated links to Danish translation would fall back to showing English content

Actual result:

English URI: /en/foo
Danish URI: /da/foo

And requesting /da/foo leads to a 404, because there is not translated page that has a slug

Possible solutions:
  1. If content fallback is configured, generate URIs like /da/?id=42 (which currently would work properly)
  2. Implement fallback in URI resolving, so that /da/foo properly resolves to page id 42 even with no slug in translation is available

Side note:

If a page translation records exists but is set to hidden everything works like expected

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.