New ordered terms do not have correct order index
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.
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