[MGNLDATA-30] When deleting a type its custom nodetype definition should be deleted too Created: 24/Jun/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Will Scheidegger Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File patch.txt    
Issue Links:
dependency
depends upon MAGNOLIA-2824 Magnolia Provider is missing API to u... Closed
duplicate
is duplicated by MGNLDATA-105 Can neither delete nor rename data ty... Closed
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Date of First Response:

 Description   

When a type is deleted from the "Types" listing of the "Data" menu, this process also deletes the menu item configuration for this type, but leaves the nodetype definition in the custom_nodetypes.xml files. It would be nice if this would be removed too because this might cause problems when later a new type with the same name is being created.



 Comments   
Comment by Jan Haderka [ 30/Jul/09 ]

Attached patch for the issue, but until related Magnolia and JR issues are fixed, there is no point in applying it.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 05:10:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.