Love the idea of this package -- I've been for years wanting to cleanup old, unused content. I stumbled across this today while I'm trying to fix my Media in XML Data Integrity. (https://our.umbraco.org/forum/using-umbraco-and-getting-started//91064-how-to-fix-xml-data-integrity-issues-with-media-content) Not sure if it could be extended to also resolve these errors.
Upon running this on my dev sandbox I ran into a few errors with content that's in use is removed.
When we originally built our Umbraco multi-site instance a few years ago, we had what I now look back on as an odd design decision. We chose to create custom Media types and store image, crop, text, and other information in the media types. We organized these into folders by type in the backoffice, and on the Content Nodes we have a Media Picker property that points to a content folder for a Product.
So each product gets a media folder which then gets a few 'standard' types of folders added to it from hooking into the ApplicationEventHandler with some of our own OnSave logic.
Because of this we have macros wired up to look at the current page, get the ID of that media picker property, then used that to drill down to specific items by type (either folders or individual media types). Because these items weren't mapped directly or dropped directly into content nodes they're being removed. It'd be desirable if we could support this odd design usecase.
One other sort of odd thing is that I have a folder or two which host some specific content for things like marketing emails, etc. This is essentially 'static' content in my book, ideally, we could select which folders to scan and which to ignore.
Some feedback
Love the idea of this package -- I've been for years wanting to cleanup old, unused content. I stumbled across this today while I'm trying to fix my Media in XML Data Integrity. (https://our.umbraco.org/forum/using-umbraco-and-getting-started//91064-how-to-fix-xml-data-integrity-issues-with-media-content) Not sure if it could be extended to also resolve these errors.
Upon running this on my dev sandbox I ran into a few errors with content that's in use is removed.
When we originally built our Umbraco multi-site instance a few years ago, we had what I now look back on as an odd design decision. We chose to create custom Media types and store image, crop, text, and other information in the media types. We organized these into folders by type in the backoffice, and on the Content Nodes we have a Media Picker property that points to a content folder for a Product.
So each product gets a media folder which then gets a few 'standard' types of folders added to it from hooking into the ApplicationEventHandler with some of our own OnSave logic.
Because of this we have macros wired up to look at the current page, get the ID of that media picker property, then used that to drill down to specific items by type (either folders or individual media types). Because these items weren't mapped directly or dropped directly into content nodes they're being removed. It'd be desirable if we could support this odd design usecase.
One other sort of odd thing is that I have a folder or two which host some specific content for things like marketing emails, etc. This is essentially 'static' content in my book, ideally, we could select which folders to scan and which to ignore.
Best, Chris
is working on a reply...