Bug #59641
closed
Make Extbase use Repository for internal calls
Added by Felix Oertel almost 10 years ago.
Updated almost 4 years ago.
Description
When resolving request arguments, extbase does not use the corresponding repository to get the object from the database but uses it's own findByUid-method instead.
This makes it impossible to use your own querySettings for example.
Extbase should use the methods from the corresponding repository instead.
Please see my comment only as a workaround and not as a solution.
If you need f.e. hidden records you can inject the Session-Object (\TYPO3\CMS\Extbase\Persistence\Generic\Session) into your controller.
With help of an initialize method you can call your own method in Repo to retrieve hidden objects and register them in Session-Object.
Now when findByIdentifier in Repo was called, it first checks if needed records are already registered in Session-object regardless if they are hidden/deleted or what ever.
Please remember that Sessionobject is marked as deprecated and may be removed in 6.3
Stefan
- Project changed from 534 to TYPO3 Core
- Category changed from Extbase: Generic Persistence to Extbase
- TYPO3 Version set to 6.2
- Is Regression set to No
- Target version changed from 7.0 to 7.1 (Cleanup)
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
- Target version changed from 7.4 (Backend) to 7.5
- Target version deleted (
7.5)
- Status changed from New to Rejected
Also available in: Atom
PDF