1) Create a normal Feature (Base Article) with a content type and field (like Image field). Enable it, etc.
2) Make a change, such as changing the Image display setting to be Thumbnail
3) Create an Override for this change (click Override tab, enter machine name, select Image field, etc). Export it and enable it.

Verify that the Image field now displays as a thumbnail when an article is viewed.

4) Disable the Override feature in the admin/features list.

Note that the Image field in an article still displays as a thumbnail and does not automatically revert to the base settings.

This is another case where the Alter-hook method could improve things. In that method, enabling and disabling the override feature works as expected.

Comments

mpotter’s picture

mpotter commented

So, the reason this happens in Features Override but not in my other Features Override Field module is the way the alter hooks are being processed.

In Features Override, the alter hooks for each exportable are handled by the Features Override module itself. In Features Override Field, the alter hook is exported as part of the override code. So when you disable the specific override feature, the alter hook in that override gets disabled. This probably causes the field to revert to it's original form.

Changing this seems very difficult in Features Override since it was a core part of the architecture. But for overrides to really work correctly, the alter hook needs to be in the actual Override exportable code.

I suppose it might be possible in the Features Override alter hook processing to check to see if an override is disabled or not?