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

pvhee’s picture

Same issue here. Maybe something to do with #573586: Fix features integration ?

amitaibu’s picture

Project: Features » Rules
Version: 6.x-1.0-beta3 » 6.x-1.x-dev
Component: Code » Provided module integration

This is a rules issue.

fago’s picture

Status: Active » Closed (works as designed)

I 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.

q0rban’s picture

Status: Closed (works as designed) » Active

Rules appear overridden on other sites, not the install where I created the feature.

brad.bulger’s picture

confirm 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.

itangalo’s picture

Confirming that rules and rule sets appears as overridden on clean installs.

brad.bulger’s picture

i 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.

darrenmothersele’s picture

Also 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.

freelock’s picture

Subscribing

gordon’s picture

subscribing

fago’s picture

Status: Active » Fixed

I 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.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

mitchell’s picture

Component: Provided module integration » Provided Module Integrations

Updated component.