Bug #47362
open
Category Model must support items property
Added by Alexander Schnitzler over 11 years ago.
Updated almost 2 years ago.
Priority:
Won't have this time
Description
Currently the category model lacks the property "items", the relation back to all datasets which are related to a category. As this is handled through mm with tablenames the model cannot provide a property with a specific annotation like
/**
* @var ObjectStorage<Item>
*/
Therefore a mapping configuration has to be used that defines which tablename of the mm-table fits to which model. At the same time the reflection for this property has to be disabled or just not used.
Related issues
1 (1 open — 0 closed)
- Status changed from New to Accepted
- Target version changed from Extbase 6.2 to Extbase 6.3
- Assignee deleted (
Alexander Schnitzler)
- Status changed from Accepted to Needs Feedback
Hi,
was this issue fixed or does it still exists?
I fixed that in a project of mine and put the patchset here on gerrit but people didn't like my approach. So this is still valid but I guess you can't fix it at all.
- Project changed from 534 to TYPO3 Core
- Category changed from Extbase: Generic Persistence to Extbase
- Status changed from Needs Feedback to New
- Target version changed from Extbase 6.3 to 7.0
- 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)
- Priority changed from Must have to -- undefined --
This is unlikely to change soon as this needs a deep understanding of the persistence of Extbase and probably some changes to the underlying architecture at first.
- Priority changed from -- undefined -- to Won't have this time
Also available in: Atom
PDF