With the increasing number of fields in our site, I find it harder and harder to locate existing fields when creating a new content type. This patch sorts the options array before handing it to the select list. Ultimately it might be nice to group existing fields by content types they are assigned to, even if they are doubling up.
| Comment | File | Size | Author |
|---|---|---|---|
| sort_existing_fields.patch | 658 bytes | nicolash |
Comments
Comment #1
nicolash commentedUhm, nope...looks better, but doesn't work.
Comment #2
doc2@drupalfr.org commentedIs this patch supposed to solve my request? http://drupal.org/node/154490 (Screenshot included.)
Thank you.
Arsène
Comment #3
yched commented@doc2 : the issue you mention seem completely unrelated
Comment #4
doc2@drupalfr.org commentedSorry, I thought it was. I understand it better now. You can delete it including this post (I wish I could, this would avoid you to do it for me).
Comment #5
spencersundell commentedThank you, @NicolasH!! This was driving me insane. I really don't understand why this was not part of the code from the very beginning. The default sort order makes zero sense and is unusable with anything more than a handful of fields.
Although I'm using D5.7, your patch helped me locate the correct line of code to modify. You saved me and my site's admin users from needless migraines.
In my case I opted to use natcasesort so that all names sort in alpha order regardless of the case of the label's letters.
cheers
Comment #6
karens commentedField name sorting was added into a recent commit.
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.