Features Override

Features Override is used by modules that provide features to selectively enhance other features. You may want to use it if:

• You are installing a feature module that requires this module.
• You have a site built on features - e.g., an Open Atrium or Managing News site - and you want to make changes without losing them when you upgrade to a new version.
• You are a feature developer looking to selectively override components (Views, content types, etc.) of existing features and export just the changes to code.

Initial development sponsored by Chocolate Lily.

While most features component types seem to be more or less working, support for views (and, likely, panels) is unstable with several reported issues.

Requirements

• Features
• CTools

Other modules for working with Features

• See A new paradigm for overriding Drupal features for an alternative approach to overriding features.
• Features plumber can be used to remove auto-detected components from any and all features you choose.
• Features tools gives the ability to remove elements from a feature and put them back in the site database.

Instructions

See the module's documentation for how to use Features Override to save customizations to a features-based Drupal distribution like Open Atrium or Open Outreach.

The main use case for Features Override is to build new features on top of existing ones. See #876226: Export changes to feature components. To do so:

• Install and enable an existing feature. An example might be one of the Debut feature set.
• Edit one of the components supplied by that feature. For example, edit a Context to add an additional reaction or change an existing one.
• At admin/structure/features (admin/build/features in D6), click the "Override" tab and click "Add" to add a new override. Select the feature you overrode.
• Create a new feature. Under "Edit components", select "Feature override" and select the override you exported. Save the feature. This feature can now be added to sites that have the original feature you overrode.

Note that Features Override should be used only for components that can't be exported on their own. For example, fields added to a content type that's in a feature don't require Features Override--they can be exported directly to a new feature (select Edit components > field (or CCK in D6)).

Downloads