Project

General

Profile

Actions
Copy link

Bug #88562

closed

Calling setEnableFieldsToBeIgnored is ignored, when called in backend context

Added by Timo Hund over 5 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
Alexander Schnitzler
Category:
Extbase
Target version:
Candidate for Major Version
Start date:
2019-06-14
Due date:
% Done:

0%

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

Description

The QuerySettingsInterface provides a method "setEnableFieldsToBeIgnored". This provides the functionality to explicitly ignore a list of enabled fields and requires to can setIgnoreEnableFields(TRUE) before.

The logic is evaluated in the frontend context (see. Typo3DbQueryParser::getVisibilityConstraintStatement) but it is not evaluated for the backend. The variable $enableFieldsToBeIgnored is even not passed to the method getBackendConstraintStatement.

Actions
Copy link
 #1

Updated by Timo Hund over 5 years ago

  • Category set to Extbase
  • Target version set to Candidate for Major Version
Actions
Copy link
 #2

Updated by Alexander Schnitzler over 4 years ago

  • Assignee set to Alexander Schnitzler
Actions
Copy link
 #3

Updated by Alexander Schnitzler over 4 years ago

  • Status changed from New to Rejected

What you describe is actually desired behaviour.
The backend should by default ignore enable fields to let users see disabled records e.g.

Actions
Copy link
 #4

Updated by Philipp Kitzberger almost 3 years ago

Alexander Schnitzler wrote in #note-3:

What you describe is actually desired behaviour.
The backend should by default ignore enable fields to let users see disabled records e.g.

Something's weird here ;-/

On TYPO3 11 and for our custom extbase BE module records only show up when I do this to the repository:

$query->getQuerySettings()->setIgnoreEnableFields(true);

It seems not to be the default (anymore). But it used to be like this, right?

Actions
Copy link

Also available in: Atom PDF