[MGNLCDEP-97] Removing a reference leaves orphaned ids in the system Created: 17/Aug/17  Updated: 26/Aug/22

Status: Open
Project: Content Dependencies
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: alex Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File img1.PNG    
Issue Links:
dependency
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: AuthorX Support
Team: AuthorX

 Description   

Hi, I'm currently working with a larger magnolia project where we have several custom content apps that heavily reference the categories and assets ( dam ) apps. Our issue is, when we delete a category ( in categories ) or an item ( in the custom content apps ) that reference categories or assets we now have orphaned id's as deleting from one workspace does not delete the references in the others. This is a major issue for us since we heavily use these references - we've noticed our logs fill up with ItemNotFoundExceptions to the point where it is starting to impact performance. We noticed that in the pages and assets apps, if you try to delete something you are presented with a dialog box that shows items that are referencing said item ( image attached ). Would it be possible to add an extra button/option to this dialog that removes the references with the deletion of said item or implement something that can better help us manages these orphans?



 Comments   
Comment by Adrien Manzoni [ 21/Aug/17 ]

Hi Alex,

we have a module called "content dependencies". Could you please check if it solves your problem ?

https://documentation.magnolia-cms.com/display/DOCS/Content+Dependencies+module

Best regards
Adrien

Comment by alex [ 28/Aug/17 ]

Hi Adrien,

Yes, this will definitely be of help but we were wondering/hoping if Magnolia could do more to help us manage these orphans through the category and assets apps?

Comment by Jan Haderka [ 29/Aug/17 ]

I like the idea of adding extra button to also remove all the references together with the removed item.
However consider this: when removing item, you/magnolia automatically trigger unpublishing of deleted item. However all the updated references will not be published automatically.

Comment by Adrien Manzoni [ 29/Aug/17 ]

Hi Alex,

This module is an official Magnolia module to manage dependencies during deletion.
It requires configuration, so we can definitely support you to set it up.

If this modules needs to be extended to fully cover your requirement, we can as well assist you.

Let me know if using this module is a solution for you.

Generated at Mon Feb 12 00:12:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.