Replies: 1 comment 4 replies
-
This isn't supported: #6056. You have to implement it low-level like the other Having soft-deleted content items/versions in the DB won't become a noticeable issue until you have millions, BTW (or if you need them hard deleted for compliance reasons). |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Everyone,
As I previously discussed here regarding best practices for updating/creating a Content Item using the service in DI for my API microservice, I now have a similar question about deletion.
I have noticed that the Content Manager doesn't permanently delete my
Publisher
Content Item. It only has a RemoveAsync method that unpublishes the Content Item but leaves it in the database. I'm interested in permanently deleting the Content Item because I don't use versioning, and I prefer to keep my database clean of unused content.Here is how I have implemented the method in my handler class, but as mentioned, it doesn't delete the Content Item from the database:
Here is the
Publisher
Content Type I created in the OC backoffice, andVersionable
is turned off:It seems that this topic was also discussed in the past, but I can't find a solution using the
ContentManager
.YesSql
Isession.Delete method? Doesn't an Orchard Core handler exist? 🤔Thank you
Beta Was this translation helpful? Give feedback.
All reactions