#47362Category Model must support items property
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.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
History 14
-
Alexander Schnitzler changed status
NewAccepted <span data-processor="relativetime" data-value="2013-05-01T22:02:39+00:00" > 05/01/13, 22:02 </span> -
Alexander Schnitzler changed target version <span data-processor="relativetime" data-value="2013-05-31T15:25:14+00:00" > 05/31/13, 15:25 </span>
-
Alexander Schnitzler changed removed the assignee <span data-processor="relativetime" data-value="2014-01-13T20:25:13+00:00" > 01/13/14, 20:25 </span>
-
Alexander Opitz commented and changed status
AcceptedNeeds Feedback <span data-processor="relativetime" data-value="2014-09-23T12:16:20+00:00" > 09/23/14, 12:16 </span> -
Alexander Schnitzler commented <span data-processor="relativetime" data-value="2014-09-23T12:26:41+00:00" > 09/23/14, 12:26 </span>
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.
-
Alexander Schnitzler commented <span data-processor="relativetime" data-value="2014-09-23T12:30:41+00:00" > 09/23/14, 12:30 </span>
This was the patch: https://review.typo3.org/#/c/20035/
-
Alexander Opitz commented and changed project id category status
Needs FeedbackNew target version TYPO3 Version 6.2 Is Regression 0 <span data-processor="relativetime" data-value="2014-09-23T14:36:31+00:00" > 09/23/14, 14:36 </span> -
Mathias Schreiber changed target version <span data-processor="relativetime" data-value="2014-12-23T19:46:36+00:00" > 12/23/14, 19:46 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2015-06-15T17:44:55+00:00" > 06/15/15, 17:44 </span>
-
Susanne Moog changed target version <span data-processor="relativetime" data-value="2015-08-05T10:24:30+00:00" > 08/05/15, 10:24 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2015-09-24T19:21:52+00:00" > 09/24/15, 19:21 </span>
-
Alexander Schnitzler commented and changed priority
Must have-- undefined -- <span data-processor="relativetime" data-value="2020-02-28T16:57:30+00:00" > 02/28/20, 16:57 </span>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.
-
Christian Kuhn changed priority
-- undefined --Won't have this time <span data-processor="relativetime" data-value="2023-01-06T12:28:37+00:00" > 01/06/23, 12:28 </span> -
Christian Kuhn commented and changed status
NewClosed <span data-processor="relativetime" data-value="2024-12-04T14:32:23+00:00" > 12/04/24, 14:32 </span>Hey. I’m going to close this stalled issue. v13 still has a category model without items, but i’m unsure which other progress happened around MM stuff in extbase meanwhile. I think we should restart with a fresh issue in case this is picked up again.
Hi,
was this issue fixed or does it still exists?