Bug #77754

Typo3DbQueryParser does not respect enablefields for translated objects

Added by Ruben Schmidmeister about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2016-09-01
Due date:
% Done:

0%

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

Description

The method getSysLanguageStatement adds the deleted clause in the subquery for selecting the default uids from the l10n_parent field but it does not respect the enablefields (hidden, startdate, ...)

This causes problems when the translated record is set to hidden but the record in the original language is not.

Example (tx_news):

1. Place a list plugin with limit = 1, sortby = date descending
2. Create a new news in the default language (make sure that it shows up)
3. Translate the news to any other language (and enable it)

4. Create a new news in the default language with a newer date (make sure that it shows up)
5. Translate the news to any other language (and leave it disabled)

6. In the frontend switch to the other language.

Expected Behaviour:
- The non-hidden translated news record is shown.

Actual Behaviour:
- No news record is shown.


Related issues

Related to TYPO3 Core - Bug #62921: l10n_mode with relations does not work in ExtbaseClosed2014-11-13

Actions
#1

Updated by Wouter Wolters about 5 years ago

Thanks for the report. There are quite a few tickets already about language handling in extbase and the problems there.

I close this one now in favor of the already existing tickets. Please continue in https://forge.typo3.org/issues/77298

#2

Updated by Wouter Wolters about 5 years ago

  • Status changed from New to Closed

Also available in: Atom PDF