I had a couple of Nodequeues added to a feature and was finding that they were showing up as 'Overridden' even though I hadn't really made any changes. Reverting the feature didn't affect this status. It turns out that the entries for a queue in the nodequeue_roles and nodequeue_types tables maybe stored in a different order to what's specified in the features's default settings. The order in which the data is stored doesn't really affect functionality but it does affect the Feature's status because Features module uses MD5 hashes (of the code required to create each nodequeue) to work out what has and hasn't changed.
To fix this issue we simply need to ignore the ordering of the items in the 'roles' and 'types' arrays. We do this by sorting these arrays once loaded in the the fe_nodequeue_queue_features_export_render() method.
Patch attached.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | fe_nodequeue_842528_array_ordering_update.patch | 878 bytes | wizonesolutions |
| #2 | fe_nodequeue-array-ordering-update.patch | 1.16 KB | 13rac1 |
| #2 | fe_nodequeue-array-ordering-879588-769660.patch | 796 bytes | 13rac1 |
| fe_nodequeue-array-ordering.patch | 1018 bytes | hiddentao |
Comments
Comment #1
hiddentao commentedComment #2
13rac1 commentedPatch fixes broken "Overridden" status on features supplying Nodequeues. Two files attached:
Applying all three to current dev:
Comment #3
kmontysub
Comment #4
wizonesolutionsThank you for the contribution! Committed to 6.x-1.x (modified patch attached).
Comment #5
wizonesolutionsActually, this might need porting. toleillo, if this is not an issue in 7.x-1.x, please mark fixed.
Comment #6
toleillo commentedPatch: http://drupal.org/node/842458#comment-4578594 on 7x branch.
Comment #7
pfrenssenThis has been fixed in commit 9f11aac almost two years ago.