Bug #53120

Proper fetching of records in a language in the fallback-chain

Added by Stefan Neufeind almost 6 years ago. Updated over 3 years ago.

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

0%

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

Description

  • Image a record that only exists in language 1.
  • Fallback is 2 -> 1 -> 0
  • Usually in the core records for IN (0, -1) are fetched and then overlays performed.
  • In some cases also the current language is fetched (2 here) because there might be records which only exist in 2 and have no 0.

What we currently miss in various places are records that only exist in 1 (more general: only in languages inside the fallback-chain, not existing in 0 or the current language).

This turned up during the review of https://review.typo3.org/23905 but is imho a too general problem in various areas of the core as to fix it just in that one patch. We might need some tool-function to create a proper condition (like with enableFields or so).


Related issues

Related to TYPO3 Core - Bug #17354: fallback for menus. "content_fallback;1,0" has no affect for page records (e.g. menu) Closed 2007-07-22

History

#1 Updated by Mathias Brodala almost 6 years ago

Isn't this related to #17354?

#2 Updated by Mathias Schreiber over 4 years ago

  • Target version set to 7.4 (Backend)

#3 Updated by Susanne Moog about 4 years ago

  • Target version changed from 7.4 (Backend) to 7.5

#4 Updated by Benni Mack almost 4 years ago

  • Target version changed from 7.5 to 7 LTS

#5 Updated by Mathias Schreiber almost 4 years ago

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

Isn't this handled by includeRecordsWithoutDefaultTranslation?

#6 Updated by Alexander Opitz over 3 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.

Also available in: Atom PDF