Bug #86627

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

Added by Chris Müller 2 months ago. Updated about 1 month ago.

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

100%

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.

Associated revisions

Revision ec2340a6 (diff)
Added by Benni Mack about 1 month ago

[BUGFIX] Include DB queries with free mode records

With the new site handling, the overlayType for fetching
records in the frontend context is always set to
OVERLAYS_ON_WITH_FLOATING, which resolves to
the previous TypoScript settings:
- config.sys_language_overlay = 1
- styles.content.get.select.includeRecordsWithoutDefaultTranslation = 1

However, the place where "includeRecordsWithoutDefaultTranslation"
is evaluated does not check for the actual
Language Aspect of the Context API, which makes
it impossible to fetch records without "l10n_parent" = (free mode), except for setting this option
explicitly on each TypoScript "select." query.

The patch moves the functionality into a separate method,
which allows to better unit test all options.

Resolves: #86627
Releases: master
Change-Id: I3a9005dcf13ddd26962da0d2ed930929c3f3b288
Reviewed-on: https://review.typo3.org/58859
Tested-by: TYPO3com <>
Tested-by: Chris Müller <>
Reviewed-by: Chris Müller <>
Reviewed-by: Anja Leichsenring <>
Tested-by: Anja Leichsenring <>

History

#1 Updated by Wouter Wolters 2 months ago

  • Assignee deleted (Susanne Moog)

#2 Updated by Chris Müller 2 months 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 about 2 months 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 about 2 months ago

  • Sprint Focus set to On Location Sprint

As workaround: `select.includeRecordsWithoutDefaultTranslation = 1`

#5 Updated by Gerrit Code Review about 1 month 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 about 1 month 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 about 1 month ago

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

Also available in: Atom PDF