Patch (to be ported)
Project:
Features
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Jun 2011 at 05:23 UTC
Updated:
12 Mar 2015 at 19:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
seanberto commentedSubscribe. Also, wondering if this is actually a ctools issue.
Comment #2
hefox commentedI don't believe ctools is being used to handle fields -- it's not in 6 and doesn't look like it's changed for 7.
Comment #3
fearlsgroove commentedAttached patch excludes "allowed_values" from the sort that's applied to field export arrays.
Comment #4
hefox commentedLooks good and seems to function correctly.; only problem would be if another setting had a sub element that happen to have an allowed values key, but that seems like a low probability.
(Though, thinking it, may later need a hook so modules could tell features not to re-order some of their items (based on something hierarchical?, but shrug.)
Comment #5
tunicSame problem here, and I swear I have not little number of option to resort :D
#3 patch looks good but as hefox says may problems if there're subelements. That's not the case for the allowed_values element AFAIK. Anyway I've roll a patch that avoids sorting but process child elements (if any). An array with the blacklisted values is included, so it's easy to add array keys that must not be sorted (but its child might).
Comment #6
febbraro commentedPatch in #5 committed to 7.x branch http://drupalcode.org/project/features.git/commit/255b021
Id this also needed for D6?
Comment #7
hefox commentedI've never seen it happen with 6.x, but I'll look into it to see if there's a possibility. thanks
Comment #8
hefox commented