Project

General

Profile

Actions

Bug #19275

closed

TypoScript objects CONTENT and RECORDS do not respect localization of table pages

Added by Oliver Hader about 16 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2008-09-02
Due date:
% Done:

0%

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

Description

Imagine someone wants to display the localized title of a page in FE by the RECORDS object in TypoScript - example:

temp.pageTitle = RECORDS
temp.pageTitle {
source = pages_123
tables = pages
conf.pages < lib.whatever
}

In tslib_cObj there's a call to $GLOBALS['TSFE']->sys_page->getRecordOverlay() which won't work for pages, since pages have an own table for localization stuff - thus getPageOverlay() would be correct for the table 'pages' in the RECORDS and CONTENT TS-object...

Further reasons:
  • pages don't have [ctrl][languageField]
  • missing the check and handling for [ctrl][transForeignTable]

(issue imported from #M9275)


Files

0009275.patch (5.43 KB) 0009275.patch Administrator Admin, 2008-09-02 22:08
0009275_v2.patch (5.53 KB) 0009275_v2.patch Administrator Admin, 2008-09-03 09:36

Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #23222: CONTENT TS object fails to show translations of pages DB tableClosed2010-07-18

Actions
Related to TYPO3 Core - Bug #17450: No language overlay with TS select on table pagesClosedTolleiv Nietsch2007-07-07

Actions
Related to TYPO3 Core - Bug #42279: RECORDS content object does not fetch translations for pagesClosed2012-10-22

Actions
Actions

Also available in: Atom PDF