I've created a simple override of a context which has one deletion and one addition. I decided that I don't want the addition so I deleted it from code in the *.features_override.inc
file. I cleared the cache and expected the feature I was overriding to show that the context was overridden. However I see that the context is shown as default and that my overrides module is now overridden, adding back in the addition I deleted from code.
The primary benefit I see for features_override is for providing a UI to calls such as hook_context_default_contexts_alter()
and other _alter()
hooks which can take some time to craft. But if I can't update the code in an overrides module I'd rather go back to crafting these alter hooks and knowing I can always update them without ever touching the db.
Comments
Comment #1
nedjoLike any time you've made an edit in code to a features compontent and want your change to show up, you need to revert any overrides--in this case, the feature override you created. That should get you what you're wanting.
In general when creating features, the following is a good workflow:
Then for each subsequent change:
That keeps your features clean and in their default state.