The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Currently, API compatibility terms are generated in the order of most recent to earliest (ie. 6.x to 4.0.x). They need to be generated in chronological order (ie. 4.0.x to 6.x). Attached patch fixes this.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | dot_api_term_order_4.patch | 1.26 KB | aclight |
| #2 | dot_api_term_order_2.patch | 971 bytes | aclight |
| dot_api_term_order.patch | 896 bytes | aclight |
Comments
Comment #1
dwwSure. Might as well add 7.x while you're at it.
Comment #2
aclight commentedYep, might as well. Here's an updated patch. I haven't yet tested this updated patch.
Comment #3
dwwActually, if what you're worried about is the order of the terms, I'm pretty sure you need to specify the weight for each term, not just change the order they're submitted in. Since we want a reverse chronology order in the various term listings, we want to weight the oldest terms the heaviest and keep getting lighter as we get newer. That's actually how the code worked during the initial conversion to the "new" release system...
Comment #4
aclight commentedYep, good point. This does the trick.
Comment #5
dwwGreat, ship it. Thanks!
Comment #6
aclight commentedFixed in http://drupal.org/cvs?commit=116521
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.