Bug #86627

Translations for content elements using free mode not shown anymore in frontend in v9

Added by Chris Müller about 3 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2018-10-11
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:
On Location Sprint

Description

Given is a site management configuration with two languages:

rootPageId: 3
base: 'https://www.example.net/'
baseVariants:
 -
   base: 'http://example.ddev.local:8080/'
   condition: 'applicationContext == "Development"'
 -
   base: 'https://staging.example.net/'
   condition: 'applicationContext == "Production/Staging"'
 -
   base: 'http://testing.example.net/'
   condition: 'applicationContext == "Testing"'
languages:
 -
   title: English
   enabled: true
   languageId: '0'
   base: /en
   typo3Language: default
   locale: en_US.utf8
   iso-639-1: en
   navigationTitle: English
   hreflang: en
   flag: us
 -
   title: Deutsch
   enabled: true
   languageId: '1'
   base: /de
   typo3Language: de
   locale: de_DE.utf-8
   iso-639-1: de
   navigationTitle: Deutsch
   hreflang: de
   fallbackType: strict
   flag: de
errorHandling:
 -
   errorCode: '404'
   errorHandler: Page
   errorContentSource: 't3://page?uid=96'
routes:
 -
   route: sitemap.xml
   type: uri
   source: 't3://page?uid=3&type=1533906435'

For the translations of the content elements I am using the free mode. Result is now, that no content elements on the translated page are shown.

#1

Updated by Wouter Wolters about 3 years ago

  • Assignee deleted (Susanne Moog)
#2

Updated by Chris Müller about 3 years ago

  • Subject changed from Translations for content elements not shown in free mode to Translations for content elements using free mode not shown anymore
#3

Updated by Chris Müller almost 3 years ago

  • Subject changed from Translations for content elements using free mode not shown anymore to Translations for content elements using free mode not shown anymore in frontend in v9
#4

Updated by Susanne Moog almost 3 years ago

  • Sprint Focus set to On Location Sprint

As workaround: `select.includeRecordsWithoutDefaultTranslation = 1`

#5

Updated by Gerrit Code Review almost 3 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58859

#6

Updated by Gerrit Code Review almost 3 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58859

#7

Updated by Benni Mack almost 3 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#8

Updated by Benni Mack over 2 years ago

  • Status changed from Resolved to Closed
#9

Updated by Johannes Rebhan almost 2 years ago

If fallbackType: fallback is used the free modes stops displaying any content altogether. fallbackType has to be set to strict for free mode to work. This feels wrong and confusing, as a robust, fallback based configuration only seems to work now with Connected Mode.

Therefore I would not consider this one as fixed. Only partially.

#10

Updated by Tobias Gaertner 9 months ago

Still (TYPO3 9.5.23) the behaviour is weired.

Setting a translation language to fallbackType: strickt
results in free contents (no l18n_parent) are still displayed...

Also available in: Atom PDF