Project

General

Profile

Bug #3207

Recursive category delete in category manager

Added by Anonymous over 10 years ago. Updated almost 10 years ago.

Status:
Bug resolved
Priority:
Normal
Assignee:
-
Target version:
Start date:
05/04/2011
Due date:
12/04/2011
% Done:

100%

Estimated time:
Complexity:
Normal

Description

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.

History

#1

Updated by Anonymous over 10 years ago

  • Due date set to 12/04/2011
  • Status changed from New to Assigned
  • Assignee set to Anonymous
  • % Done changed from 0 to 50
#2

Updated by Anonymous over 10 years ago

  • Status changed from Assigned to Needs testing
  • % Done changed from 50 to 100

Implemented!

#3

Updated by Stefaan Vanbillemont over 10 years ago

  • Target version changed from 21 to 2.1.0
#4

Updated by Stefaan Vanbillemont over 10 years ago

  • Status changed from Needs testing to Needs more info

Tested and implemented but NO warning .. it this possible to add this? And what if objects are still connected to one or more subcategories?

#5

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.

#6

Updated by Anonymous about 10 years ago

  • Status changed from Needs more info to Needs testing
#7

Updated by Sven Vanpoucke almost 10 years ago

  • Status changed from Needs testing to Bug resolved

These checks are added to repository and weblcms and should now be fixed

Also available in: Atom PDF