Actions
bug #7933
closedAdding a new Term to the "Country" vocabulary leads to corrupt data
Start date:
Due date:
% Done:
100%
Estimated time:
Severity:
critical
Found in Version:
Description
After adding a new term to the "Country" vocabulary the cdm server throws an exception during startup
Updated by Patrick Plitzner over 5 years ago
- Target version changed from Unassigned CDM tickets to Release 5.5
Updated by Patrick Plitzner over 5 years ago
- Status changed from New to Feedback
- Assignee changed from Patrick Plitzner to Andreas Müller
@Andreas: Should it be allowed at all to add a new term to the Country vocabulary?
The problem is in the TermType class which does not have a specific value for Country, thus a new NamedArea is added to the list of Countries which causes the exception.
Updated by Patrick Plitzner over 5 years ago
- Severity changed from blocker to critical
Updated by Andreas Müller over 5 years ago
- Assignee changed from Andreas Müller to Patrick Plitzner
Can we handle this special case hardcoded until the terms modul is more elaborated?
E.g. by testing if the vocabulary is explicitly the countries vocabulary and then disallow to add a term at all (adding countries should not be allowed as the vocabulary is managed).
Updated by Patrick Plitzner about 5 years ago
- Status changed from Feedback to Resolved
- Assignee changed from Patrick Plitzner to Andreas Müller
- % Done changed from 0 to 50
Fixed by hardcoding the check for the "Country" vocabulary
Updated by Andreas Müller about 5 years ago
- Status changed from Resolved to Closed
- Assignee changed from Andreas Müller to Patrick Plitzner
Ok, this seems to work as expected
Actions