Bug #59641
closed
Make Extbase use Repository for internal calls
0%
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.
Updated by Stefan Froemken almost 10 years ago
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
Updated by Alexander Jahn almost 10 years ago
I suppose this is the same isse I found in 4.7.
Take a look at this, might be of some help.
http://forge.typo3.org/issues/51245
Updated by Alexander Opitz over 9 years ago
- 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
Updated by Mathias Schreiber over 9 years ago
- Target version changed from 7.0 to 7.1 (Cleanup)
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5