Features does not recognize overrides unless it can find changed rules instead of deleted rules. [#1203480]

Essentially I was a little upset that Features was not allowing me to Revert changes in order to import Rules from the Feature into the Database.

I've discovered that if I make a change to the Rule but maintain the same machine name, Features detects the Override and offers the Revert option.

However if I modify the machine name, or delete the Rule out right, then Features does not recognize any override (but continues to offer the Rule in code) and thus does not provide a means to Revert the Feature and import the Rule into the database.

Even stranger is that in a feature that has 2 Rules (both use the same category). If I modify Rule_A in order to force the override/revert option, and delete Rule_B, both the Rule_A modification and Rule_B disappearance are displayed in Review Overrides. Unfortunately the Revert option, while available, reports success, but does not actually revert anything.

Comments

Comment #1

Crom commented 29 June 2011 at 19:34

Yes, I have the same problem here. I want to export a feature (containing an exported rules category) and then re-import it into the same site to do further refinement/bugfixing etc. when I activate the feature it is immediately classed as 'overridden' and if I look in the rules config screen I get the WSOD and loads of offset errors in watchdog.

There seem to be plenty of reports of this elsewhere in the issues queue and it appears that there is a problem with integrating rules that already exist on the site with those that exist in a feature.

I tried updating to 6.x dev version but same problem exists (just a slightly different line number in the watchdog report).