Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.feature revert for an exported rules didn't work for me using latest dev version, though reverting using the rules ui worked fine
Comments
Comment #1
fagoI tracked the bug down - the problem is not reverting but that it just appears always as overridden.
See #1062526: components appear always overridden if the default hook makes use of a hook-group for the bugfix.
Comment #2
fagoComment #3
dasjoyep, reverting works. also features containing rules are detected to be overridden/default correctly.
so, i guess we just need the rules ui to reflect this correctly :)
Comment #4
fagoWith the mentioned issue committed, this should be fixed. Please re-open if there are still troubles.
Comment #5
dasjoas stated, features correctly detects the rules-containing feature to be in default state.
the problem is, that that the rules ui itself shows the rule with status overridden. one has to manually revert the rule in order to set it to state default.
this may not really a bug, but more a question of consistency: from my understanding rules' interpretation of "overridden" is "lives in db, may equal to version code" while features interpretation of overridden is "lives in db and is different from code"
Comment #6
fagoI see. I think the problem here is that you still have the originally created rule in the db when the feature is activated, thus it is marked as overridden. Not sure how this could work though, isn't it the same for other exportables e.g. views?
Comment #7
dasjoi just checked: in views, if i revert a view its state is being set to default again. the same is true for feeds
Comment #8
fagooh, sry I see what's your problem now. However, reverting rules works fine for me? Maybe, the overridden status has been exported in you rule?
Comment #9
dasjohmm seems to work now :)
Comment #11
mitchell commentedMoving to "Provided Module Integrations" component.