The child-references of a record are not marked as deleted if enableCascadingDelete is TRUE #26
-
Lets say we have the following record relation: a book (parent) has multiple chapters (children), defined like this: TCA configuration:
Model: Book.php
The request I tried it also with the replaced annotation |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Extbase uses some things from TCA configuration but does not reflect all the features. As far as I know (can't test it at the moment) this one is not reflected and that's why it works for you only in backend. To achieve cascade remove on Extbase you need to use its annotation:
Regarding cascade persistence annotation from t3api - it's just security enhancement of Extbase as Extbase does not support any other cascade than remove, unfortunately. We hope some day we can remove it and relay on pure Extbase also for persistence. Here you can find more info and example usage of cascade persistence. Please try it with Extbase's cascade remove annotation and let us know if it worked. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
Yes indeed, that works. Thank you very much for the explanation and sorry for opening the ticket than. Just was a bit confused 👍 |
Beta Was this translation helpful? Give feedback.
Extbase uses some things from TCA configuration but does not reflect all the features. As far as I know (can't test it at the moment) this one is not reflected and that's why it works for you only in backend. To achieve cascade remove on Extbase you need to use its annotation:
Regarding cascade persistence annotation from t3api - it's just security enhancement of Extbase as Extbase does not support any other cascade than remove, unfortunately. We hope some day we can remove it and relay on pure Extbase also for persistence. Here you can find more info and example usage of cascade persistence.
Please try it wi…