Project

General

Profile

Actions

Bug #42279

closed

RECORDS content object does not fetch translations for pages

Added by Helmut Hummel about 12 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
Start date:
2012-10-22
Due date:
% Done:

100%

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

Description

The RECORDS content object does a versioning and language overlay, but does not take the pages table into account.

Use the following TS to reproduce:

page.1 = RECORDS
page.1.source = 1
page.1.tables = pages
page.1.dontCheckPid = 1
page.1.conf.pages = TEXT
page.1.conf.pages {
field = title
htmlSpecialChars = 1
}

Even if page id is translated to a different language, the value of the default language is used.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #19275: TypoScript objects CONTENT and RECORDS do not respect localization of table pagesClosed2008-09-02

Actions
Is duplicate of TYPO3 Core - Bug #28564: Language overlay for RECORDSClosed2011-07-29

Actions
Actions #1

Updated by Gerrit Code Review about 12 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15885

Actions #2

Updated by Helmut Hummel about 12 years ago

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

Updated by Thorsten Kahler about 12 years ago

Please don't backport this change: it will surely break existing sites!

Actions #4

Updated by Helmut Hummel about 12 years ago

Thorsten Kahler wrote:

Please don't backport this change: it will surely break existing sites!

Can you please give examples what will break?

Actions #5

Updated by Thorsten Kahler about 12 years ago

Maybe you can figure out by yourself what will happen if you don't get the pages record (any more) you requested (configured/selected/...) but a translation of it in the current language...

Fixing this bug in released versions would change a behaviour which exists since many TYPO3 versions.

Actions #6

Updated by Karsten Nowak (undkonsorten) about 12 years ago

I'd like to use the patch, but i don't found the folder "frontend" in my sysext folder.
My TYPO3 version is 4.7.7

Actions #7

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF