RE: Protecting critical content and improving auditing with Delete plug-ins

Dipo Ajose-Coker — Tue, 10 Jun 2025 17:01:16 GMT

Hey Andriy, excellent post, and you have inspired me to create a What if...? blog post on this idea. I'll send you a link when it's published. In the meantime enjoy some other What if...? moments here: https://www.linkedin.com/feed/update/urn:li:activity:7338248784239284224

RE: Protecting critical content and improving auditing with Delete plug-ins

Alvin Reyes — Mon, 02 Jun 2025 19:45:19 GMT

Nice post, Andriy!

I like the idea of allowing deletion requests by users which can then be acted on by other users (or perhaps automated). I've seen a CMS setup (in Tridion Sites) where deletions were not allowed by regular users, so even accidentally copy-and-paste errors or test content needed a manual request to an admin to remove the content.

A real business requirement would be to be able to research and possibly restore any content that has been made public before. This often comes up with as part of a regulatory requirement to retain content that has potentially been seen by the public for a certain number of years. So being able to programmatically "catch" and handle a deletion request is a more nuanced and user-friendly approach to meeting the actual legal requirement.

And good reminder on the dependencies between publication, version, and language. Dependencies make deletions tricky. [emoticon:c4563cd7d5574777a71c318021cbbcc8]