Actions
Bug #87121
closedContent fallback does not work, when page translation does not exist yet
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-12-11
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
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:- If content fallback is configured, generate URIs like /da/?id=42 (which currently would work properly)
- 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
Updated by Helmut Hummel almost 6 years ago
- Is duplicate of Bug #86595: No Language Fallback added
Updated by Helmut Hummel almost 6 years ago
- Is duplicate of Bug #86762: Site-Configuration defined language fallbacks not working added
Updated by Helmut Hummel almost 6 years ago
- Status changed from New to Closed
yes indeed. closed as duplicate
Actions