Return to Answer

You may try Features Cleanup sandbox module (GH fork) as add-on to Features which can do cleanup of fields, vocabularies, panel nodes, mini panels, and image styles that are in the database, but not in any enabled features module.

This is potentially dangerous module, since it can irreversibly delete database components once they got removed from the Features, so you should test it first if that meets your expectations and it has been tested with your deployment plan and scripts.

This module is separated into two different tasks:

• Resolve Overrides

  You will have new option Resolve All Overrides at the bottom of Feature's overview screen which will attempt to cleanup all overrides by deleting existing database components (mainly fields). After that, it will revert this feature.

• Delete existing components that are not in any Features modules

  This includes: content types, mini panels, node panels, taxonomy vocabularies, image styles, etc.

  Before doing it, you need to enable all features that you want to compare against. Then click on Features Cleanup in the Features listing screen.

This module also has drush integration and provides the following commands:

• drush fcf/drush features-cleanup-all

  Cleans out all content types, panel pages, mini panels, vocabularies, and image styles from database based on existing enabled features and run features-revert-all afterwards. This is useful to include as part of your deployment process before you backup your database.

• drush fcf/drush features-cleanup-feature [feature name] [component list]

  Attempts to resolves all overrides on a single feature module. Run features-revert afterwards.

You may try Features Cleanup sandbox module (GH fork) as add-on to Features which can do cleanup of fields, vocabularies, panel nodes, mini panels, and image styles that are in the database, but not in any enabled features module.

This is potentially dangerous module, since it can irreversibly delete database components once they got removed from the Features, so you should test it first if that meets your expectations and it has been tested with your deployment plan and scripts.

This module is separated into two different tasks:

• Resolve Overrides

  You will have new option Resolve All Overrides at the bottom of Feature's overview screen which will attempt to cleanup all overrides by deleting existing database components (mainly fields). After that, it will revert this feature.

• Delete existing components that are not in any Features modules

  This includes: content types, mini panels, node panels, taxonomy vocabularies, image styles, etc.

  Before doing it, you need to enable all features that you want to compare against. Then click on Features Cleanup in the Features listing screen.

This module also has drush integration and provides the following commands:

• drush fca/drush features-cleanup-all

  Cleans out all content types, panel pages, mini panels, vocabularies, and image styles from database based on existing enabled features and run features-revert-all afterwards. This is useful to include as part of your deployment process before you backup your database.

• drush fcf/drush features-cleanup-feature [feature name] [component list]

  Attempts to resolves all overrides on a single feature module. Run features-revert afterwards.

You may try Features Cleanup sandbox module as add-on to Features which can do cleanup of fields, vocabularies, panel nodes, mini panels, and image styles that are in the database, but not in any enabled features module.

This is potentially dangerous module, since it can irreversibly delete database components once they got removed from the Features, so you should test it first if that meets your expectations and it has been tested with your deployment plan and scripts.

This module is separated into two different tasks:

• Resolve Overrides

  You will have new option Resolve All Overrides at the bottom of Feature's overview screen which will attempt to cleanup all overrides by deleting existing database components (mainly fields). After that, it will revert this feature.

• Delete existing components that are not in any Features modules

  This includes: content types, mini panels, node panels, taxonomy vocabularies, image styles, etc.

  Before doing it, you need to enable all features that you want to compare against. Then click on Features Cleanup in the Features listing screen.

This module also has drush integration and provides the following commands:

• drush features-cleanup

  Run the cleanup task and run features-revert-all afterwards. This is useful to include as part of your deployment process before you backup your database.

• drush features-resolve-override [feature name] [component list]

  Resolves overrides for features modules. This will run features-revert on the given feature.

You may try Features Cleanup sandbox module (GH fork) as add-on to Features which can do cleanup of fields, vocabularies, panel nodes, mini panels, and image styles that are in the database, but not in any enabled features module.

This is potentially dangerous module, since it can irreversibly delete database components once they got removed from the Features, so you should test it first if that meets your expectations and it has been tested with your deployment plan and scripts.

This module is separated into two different tasks:

• Resolve Overrides

  You will have new option Resolve All Overrides at the bottom of Feature's overview screen which will attempt to cleanup all overrides by deleting existing database components (mainly fields). After that, it will revert this feature.

• Delete existing components that are not in any Features modules

  This includes: content types, mini panels, node panels, taxonomy vocabularies, image styles, etc.

  Before doing it, you need to enable all features that you want to compare against. Then click on Features Cleanup in the Features listing screen.

This module also has drush integration and provides the following commands:

• drush fcf/drush features-cleanup-all

  Cleans out all content types, panel pages, mini panels, vocabularies, and image styles from database based on existing enabled features and run features-revert-all afterwards. This is useful to include as part of your deployment process before you backup your database.

• drush fcf/drush features-cleanup-feature [feature name] [component list]

  Attempts to resolves all overrides on a single feature module. Run features-revert afterwards.

You may try Features Cleanup sandbox module as add-on to Features which can do cleanup of fields, vocabularies, panel nodes, mini panels, and image styles that are in the database, but not in any enabled features module.

This is potentially dangerous module, since it can irreversibly delete database components once they got removed from the Features, so you should test it first if that meets your expectations and it has been tested with your deployment plan and scripts.

This module is separated into two different tasks:

• Resolve Overrides

  You will have new option Resolve All Overrides at the bottom of Feature's overview screen which will attempt to cleanup all overrides by deleting existing database components (mainly fields). After that, it will revert this feature.

• Delete existing components that are not in any Features modules

  This includes: content types, mini panels, node panels, taxonomy vocabularies, image styles, etc.

  Before doing it, you need to enable all features that you want to compare against. Then click on Features Cleanup in the Features listing screen.

This module also has drush integration:

• features-cleanup

  Run the cleanup task and run features-revert-all afterwards. This is useful to include as part of your deployment process before you backup your database.

• drush features-resolve-override [feature name] [component list]

  Resolves overrides for features modules. This will run features-revert on the given feature.

You may try Features Cleanup sandbox module as add-on to Features which can do cleanup of fields, vocabularies, panel nodes, mini panels, and image styles that are in the database, but not in any enabled features module.

This is potentially dangerous module, since it can irreversibly delete database components once they got removed from the Features, so you should test it first if that meets your expectations and it has been tested with your deployment plan and scripts.

This module is separated into two different tasks:

• Resolve Overrides

  You will have new option Resolve All Overrides at the bottom of Feature's overview screen which will attempt to cleanup all overrides by deleting existing database components (mainly fields). After that, it will revert this feature.

• Delete existing components that are not in any Features modules

  This includes: content types, mini panels, node panels, taxonomy vocabularies, image styles, etc.

  Before doing it, you need to enable all features that you want to compare against. Then click on Features Cleanup in the Features listing screen.

This module also has drush integration and provides the following commands:

• drush features-cleanup

  Run the cleanup task and run features-revert-all afterwards. This is useful to include as part of your deployment process before you backup your database.

• drush features-resolve-override [feature name] [component list]

  Resolves overrides for features modules. This will run features-revert on the given feature.