Bug #83296

Doctrine respects wrong storage PIDs for sys_category

Added by Stefan Froemken about 3 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2017-12-12
Due date:
% Done:

0%

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

Description

Hello,

our events2 extensions does not show any records in frontend after upgrading to current TYPO3 8.

We found out, that the executed SQL includes an additional WHERE-Statement to "sys_category.pid IN (3)". But we don't have any sys_category records in this storage folder. The storage folder with UID 3 includes event records only. For our categories we have created an additional storage folder with UID 12.

It works if we append UID 12 to the list of plugin.tx_events2.persistence.storagePid.

We are using the CategoryRepository from extbase which has an initializeObject method where respectStoragePage was set to false. In Typo3DbQueryParser->addTypo3Constraints the QuerySettings of my Repository was used for ALL related repositories incl. sys_category. This is a new behaviour.

Is there still a possibility to respect individual repository QuerySettings?

Stefan

No data to display

Also available in: Atom PDF