I have a feeling this is related to #597326: Updating feature creates duplicate rules.
If a feature contains rules, that feature always appears as overridden on admin/build/features. I've attached a screenshot of a portion of the diff.
I have a feeling this is related to #597326: Updating feature creates duplicate rules.
If a feature contains rules, that feature always appears as overridden on admin/build/features. I've attached a screenshot of a portion of the diff.
Comments
Comment #1
pvhee commentedSame issue here. Maybe something to do with #573586: Fix features integration ?
Comment #2
amitaibuThis is a rules issue.
Comment #3
fagoI think you shouldn't activate a feature on the site you built it. If you enable it on a clean site it should work right.
Comment #4
q0rban commentedRules appear overridden on other sites, not the install where I created the feature.
Comment #5
brad.bulger commentedconfirm that this happens on a clean install.
also, I think you shouldn't activate a feature on the site you built it is just not a practical requirement. my development site is an advance copy of my live site. once the feature is released, i must have it running on my development site, and i must be able to update it and change it. i think this is a pretty typical setup.
Comment #6
itangalo commentedConfirming that rules and rule sets appears as overridden on clean installs.
Comment #7
brad.bulger commentedi may be misreading the Features API, but looking at the code, and comparing it to how the similar functions work for other modules, it looks to me like rules_features_export() and rules_features_export_render() are each doing what the other function ought to, more or less: export_render ought to be returning a representation of the rules, rule_sets, etc as code (in a string, but still), but instead is just returning the names; export ought to be returning the names of the rules, rule_sets, etc., but is instead returning code (for rules, at least - i didn't have any rule sets to test it on). i can try to get into this more thoroughly. from looking at some of the other related issues, though, like #419644: Use CTools to export, i have a sense that it might be more complicated than it looks. so maybe best to hear what you all have to say about it first.
Comment #8
darrenmothersele commentedAlso experiencing this, and concur with #7. When I view the "review overrides" page I see the correct export code on the left under "Default", but just the name of the rule on the right under "Overrides". rules_categories and rules_sets both show as FALSE on right hand side under "Overrides".
The updated feature seems to contain the correct definition, not the empty version that shows up as the override on the "review overrides" page.
Comment #9
freelockSubscribing
Comment #10
gordon commentedsubscribing
Comment #11
fagoI just overhauled the features integration, see http://drupal.org/cvs?commit=338456. Please test the dev snapshot generated this night - it should be fixed there. If not please reopen.
Comment #13
mitchell commentedUpdated component.