Actions
bug #9477
closedNew ordered terms do not have correct order index
Start date:
Due date:
% Done:
100%
Estimated time:
Severity:
normal
Found in Version:
Description
If a new term is added to a new ordered term vocabulary the term is not put to the correct position. Instead it is moved to the end but has the same orderindex as the currently last term.
An example are PresenceAbsenceTerms
SELECT dtb.id, dtb.uuid, dtb.titleCache, dtb.orderIndex, voc.uuid, voc.id, voc.titleCache FROM DefinedTermBase dtb INNER JOIN TermCollection voc ON voc.id = dtb.vocabulary_id WHERE voc.uuid = 'adbbbe15-c4d3-47b7-80a8-c7d104e53a05' ORDER BY dtb.orderIndex
We need an update script for all terms that were added this way. => #9784
Also the term loader needs to be fixed to avoid this bug for new terms.
Related issues
Updated by Andreas Müller almost 3 years ago
- Related to bug #8858: Ordering of distribution status 'undefined' is not correct in E+M added
Updated by Andreas Müller almost 3 years ago
- Related to feature request #9500: Allow removing certain distribution status from distribution publication added
Updated by Andreas Müller about 2 years ago
- Related to bug #6343: TermVocabularies of OrderedTerms must be OrderedVocabularies added
Updated by Andreas Müller about 2 years ago
- Target version changed from CDM UML 5.42 to Release 5.27
Updated by Andreas Müller about 2 years ago
- Related to deleted (feature request #9500: Allow removing certain distribution status from distribution publication)
Updated by Andreas Müller about 2 years ago
- Copied to bug #9784: Update script for term order of ordered CDM terms added
Updated by Andreas Müller about 2 years ago
- Description updated (diff)
- Status changed from New to Resolved
- % Done changed from 0 to 50
before closing check on production if it worked correctly. I already tested locally.
SELECT id, dtb.orderIndex, dtb.titleCache FROM DefinedTermBase dtb WHERE dtb.DTYPE = 'Rank' ORDER BY dtb.orderIndex
Updated by Andreas Müller about 2 years ago
- Related to feature request #9778: Add new rank terms lusus, subgrex and subproles added
Updated by Andreas Müller about 2 years ago
- Priority changed from New to Highest
- % Done changed from 50 to 80
Updated by Andreas Müller about 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 80 to 100
Updated by Andreas Müller about 2 years ago
- Related to bug #9831: Exception in TermRepresentationUpdater if term does not exist added
Actions