Project

General

Profile

Actions

Feature #24005

closed

cObject CONTENT does not allow to fetch records that have no translation parent

Added by Benni Mack over 13 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
TypoScript
Target version:
Start date:
2010-11-10
Due date:
% Done:

100%

Estimated time:
PHP Version:
5.3
Tags:
Complexity:
Sprint Focus:

Description

When you fetch records through the TypoScript object "CONTENT" (or, let's say through ".select" in general), you have an option called "languageField" in order to fetch only records that match the current language.

What "select" does here is that it fetches all records in the default language ("0,-1") and then overlays them with the records of the current language.

However, it's not possible to fetch the records that don't have a localization parent.

The patch introduces a new option called "includeRecordsWithoutDefaultTranslation" that also checks for records with the languageField matching the current language, where there is no translation parent (l10n_parent = '').

(issue imported from #M16332)


Files

nodefaulttranslation.patch (1.52 KB) nodefaulttranslation.patch Administrator Admin, 2010-11-10 16:26

Related issues 1 (0 open1 closed)

Precedes TYPO3 Core - Bug #57087: Property includeRecordsWithoutDefaultTranslation of the select function misses stdWrapClosed2014-03-19

Actions
Actions

Also available in: Atom PDF