Project

General

Profile

Actions
Copy link

Bug #83216

closed

Localization do not work when "l18parent" is empty (0)

Added by Kevin Lieser almost 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Mathias Schreiber
Category:
Localization
Target version:
-
Start date:
2017-12-04
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When a content element is translated using "translate" method and so have a l18parent, the content shows up in frontend.
When using "copy" method or created the content in new language without l18parent the content do not appear in frontend.

Can simply test it when unselecting a l18parent in CE form and selecting a parent again.
See screenshots attached.

With parent, working.
Without parent, not working (not appearing in frontend).

Files

Download all files
Bildschirmfoto 2017-12-04 um 12.16.33.png (12.1 KB) Bildschirmfoto 2017-12-04 um 12.16.33.png Working Kevin Lieser, 2017-12-04 12:29
Bildschirmfoto 2017-12-04 um 12.16.17.png (8.93 KB) Bildschirmfoto 2017-12-04 um 12.16.17.png Not working Kevin Lieser, 2017-12-04 12:29
Actions
Copy link
 #1

Updated by Mathias Schreiber almost 7 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber

Can you post your complete language specific Typoscript settings here, please?
We can circle down on the issue because the field being 0 in free mode is the entire point of that field :)

Actions
Copy link
 #2

Updated by Kevin Lieser almost 7 years ago

Sorry, never noticed this setting: styles.content.get.select.includeRecordsWithoutDefaultTranslation = 1
With this, it works – so not a Bug in TYPO3 core.

Sorry!

Actions
Copy link
 #3

Updated by Mathias Schreiber almost 7 years ago

  • Status changed from Needs Feedback to Closed
Actions
Copy link

Also available in: Atom PDF