Project

General

Profile

Actions

Bug #61045

closed

RECORDS and languageField not working

Added by Stephan Bauer over 9 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-08-18
Due date:
% Done:

0%

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

Description

I'm always getting the default language:
20 = RECORDS
20 {
tables = tt_content
source = 12
languageField = sys_language_uid
}

CONTENT is working:
10 = CONTENT
10 {
table = tt_content
select {
pidInList = 3
orderBy = sorting
max = 1
languageField = sys_language_uid
}
}


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #62155: IRRE at localized records not working properly with Extbase/Fluid Rejected2014-10-10

Actions
Actions #1

Updated by Mathias Schreiber about 9 years ago

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

Could you try to set

config.sys_language_overlay = 1

Actions #2

Updated by Alexander Opitz almost 9 years ago

  • Status changed from Needs Feedback to Closed
  • Assignee deleted (Mathias Schreiber)

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions #3

Updated by Matthias Philipp over 7 years ago

The parameter "languageField" is not supported in the RECORDS object.
This query always returns the rows adressed by the source IDs, localisation depends on sys_language_overlay setting.

This behaviour might not be the expected for most users, because the CONTENT object translates in another way.

This difference should be noted in the documentation of the RECORD object.

See also https://forge.typo3.org/issues/24338

Actions

Also available in: Atom PDF