https://github.com/mxsteini/mst_contentfallback
try to fix translation fallback on content level
https://github.com/mxsteini/mst_contentfallback
contentfallback fallback fallbackchain language translation typo3
Last synced: 4 months ago
JSON representation
try to fix translation fallback on content level
- Host: GitHub
- URL: https://github.com/mxsteini/mst_contentfallback
- Owner: mxsteini
- Created: 2022-08-12T07:22:19.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2023-09-22T06:42:21.000Z (over 2 years ago)
- Last Synced: 2025-10-02T15:32:30.317Z (7 months ago)
- Topics: contentfallback, fallback, fallbackchain, language, translation, typo3
- Language: PHP
- Homepage:
- Size: 15.6 KB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: Readme.md
Awesome Lists containing this project
README
# EXT:mst_contentfallback - try to deliver the content as in siteconfiguration defined.
## Problem
At the moment (TYPO3 v11) can not deliver translations on contentlevel.
At the very moment a page is translated, you have to provide a contentelement for each transalation.
The only fallback is the 0-element.
## The fix - How the content fallback works
While these problem belongs to the basics how TYPO3 deals with translations, this approach is a workaround.
See section "Known Problem" for more ...
Asuming we have these translation
with the following content:
| en | de_DE | de_CH | es_ES | es_MX |
|-------------|-------|-------|-------|-------------|
| en0 | de0 | ch0 | es0 | mx0 |
| en1 | de1 | | es1 | mx1(hidden) |
| en2 | | | | |
| en3(hidden) | de3 | ch3 | es3 | mx3 |
results in
| en | de_DE | de_CH | es_ES | es_MX |
|-----|-------|-------|-------|-------|
| en0 | de0 | ch0 | es0 | mx0 |
| en1 | de1 | de1 | es1 | |
| en2 | en2 | en2 | en2 | en2 |
| | | | | |
only elements could be displayed which are displayed in language 0
## Installation
```json
"repositories": [
{
"type": "vcs",
"url": "https://github.com/mxsteini/mst_contentfallback.git"
}
]
```
```bash
composer req mst/mst-contentfallback
```
## Known problemes
* To deliver content, the 0-language must be part of the fallbackchain.
* workspaces are not tested
* the baselanguage-concept itself