Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It would be very nice if the source / target options were sorted alphabetically, rather than the order they are defined in the parser / processor.
here's a patch that adds asort to the _feeds_ui_format_options() results
| Comment | File | Size | Author |
|---|---|---|---|
| feeds_ui_opiton_sort_order.diff | 307 bytes | mikejoconnor |
Comments
Comment #1
mikejoconnor commentedComment #2
hazaThat could be very useful when dealing with dozen of feeds !
Tested the patch, works as expected.
Comment #3
paulgemini commentedAny plans to commit this?
Comment #4
wusel commentedI think, the sort-order should be set by the user and NOT only be sorted alphabetically.
It would be usefull, if the user can sort it, like we can sort blocks in regions manually.
Comment #5
twistor commented@wusel, This issue is only about how the select list appears on the mapping page. Not how the mapping table is arranged.
Comment #6
wusel commentedIf this issue only means the sorting on the page "/import", then i agree.
My post #4 means how the mapping table "Mapping for Node processor" should be arranged.
Comment #7
mikejoconnor commentedThe patch is for the sort order of the source and target select fields on the mapping configuration page.
Currently, I'm working on importing a feed using the Onix Standard. There are well over 50 fields that I've mapped together. The issue is simply usability related. Field names are not in a recognizable order for either the Source, or Target select boxes. This makes it time consuming, and confusing to configure a large number of mappings.
The patch above does not change any functionality, it simply improves the modules usability by placing the field names in alphabetical order.
Comment #8
kking commentedPatch added to 7.x-2.x branch. Thanks.
http://drupalcode.org/project/feeds.git/commit/2694fca
Comment #10
dave reidCommitted this to 6.x-1.x as well.