Blank custom severity in Admin panel causes traceback.

[shepting@…]

I check the boxes beside two custom severity levels in the Admin panel (on the demo hosted site) *one of which was blank* and chose to "Remove selected items".

I expected both items to be removed from the list. However, there was a traceback instead:

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.2dev_r4429-py2.4.egg/webadmin/web_ui.py", line 109, in process_request
    path_info)
  File "/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.2dev_r4429-py2.4.egg/webadmin/ticket.py", line 339, in process_admin_request
    enum.delete(db=db)
  File "/usr/lib/python2.4/site-packages/trac/ticket/model.py", line 344, in delete
    assert self.exists, 'Cannot deleting non-existent %s' % self.type
AssertionError: Cannot deleting non-existent severity}}}

I'm guessing the error stems from the fact that the severity was "blank". There isn't an error adding a severity with an empty text field (though it doesn't result in another blank severity, just the original blank one remains). However, if you try to add

[osimons]

Well, on 0.11 is does not give a traceback - small consolation. With current webadmin (built-in) it is not possible to add empty enums, but with trac-admin it is.

There is a ticket with ongoing discussions on how to prevent this situation arising, so I'm closing this ticket as 'duplicate'. Please refer to #6560 for the continuation of this issue.