Actions
Bug #91324
open
Visibility restrictions are added twice for Extbase ObjectStorage relations
Status:
New
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2020-05-06
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
In \TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbQueryParser::convertQueryToDoctrineQueryBuilder(), a \TYPO3\CMS\Core\Database\Query\QueryBuilder is created by calling \TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbQueryParser::initializeQueryBuilder(). If $source is a \TYPO3\CMS\Extbase\Persistence\Generic\Qom\JoinInterface, which is the case for ObjectStorage, default TYPO3 enablefield constraints (QueryBuilder restrictions) do not get removed. This is done when $source is not a JoinInterface.
After wards, constraints are added in \TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbQueryParser::addTypo3Constraints(), where Query::$querySettings are taken into account.
- enable field constraints are added twice to the resulting SQL query
- manipulated QuerySettings in an implementation of
\TYPO3\CMS\Extbase\Persistence\Generic\QueryFactory\QueryFactoryare ignored for relations with ObjectStorage (suggested here: https://stackoverflow.com/a/39994951/13483282)
Updated by Markus Klein almost 3 years ago
- Related to Bug #94119: Ghost record for field with mm relation when relation record is disabled added
Updated by Markus Klein almost 3 years ago
- Related to Bug #90013: Conversion of Extbase to Doctrine query disregards enable field settings for join queries (MM relations) added
Actions