Recursive category delete in category manager
The category manager deleter is not recursive, leaving subcategories when main categories are deleted.
The only way at the moment to avoid junk in the database is checking if there are subcategories and not allowing deletion.
This should be fixed so categories are deleted recursively, preferably giving a warning when subcategories are found.
Updated by Anonymous over 10 years ago
The individual applications have the method to check if a category can be deleted, if objects are linked to the subcategories the checks are performed in that context, so the subcategory will not be allowed to be deleted. The deleter stops (or at least should stop according to the code ;-)) if a subcategory cannot be deleted, so a full delete will not be propagated unless all categories can be deleted.
For the warning, because the checks are performed in the deleter component itself, and not the view, it is impossible to get a warning there. If time permits, I could alter the browser component itself to check if there are any children, but still there would rise some problems with the interface. You already have to confirm the deletion, how to apply a second confirm to it??? etc.