Users of Features have identified several scenarios in which a feature might not revert (i.e. the Manage Features page or
drush features shows the feature in the state of "Overridden"), even when all steps were taken to revert the feature to the version on file.
- Made config changes locally (to a view).
- Updated the associated Feature locally.
- Migrated the updated feature code to production.
- Attempted to revert the production feature so the new feature settings are deployed.
- Feature simply won't revert and remains overridden.
This page lists various solutions to this problem, starting with general fixes and procedures and moving on to information about specific modules and ways in which they might not be working with Features, and how to diagnose this.
Table of Contents:
- Disable and re-enable
- Missing include()
- Missing feature module files
- Problems with: Views
- Problems with: Migrate
- Problems with: Blocks (via
- Problems with: Features namespace change
- Problems with: Modules' versions changed
- Problems with: Missing dependencies
- Problem with: Feature with Rules not reverting (in 6.x)
- Problem with: Exported translatable strings
- Problem with: PHP cache
Disable and re-enable (the Silver Bullet Solution)
Read on to learn more specific scenarios and solutions, but often, disabling and reenabling the exported Feature module will do it for you. Quickest path to victory therefore is the drush one-liner:
drush dre your_module -y
The command, provided by the Devel module,
dre) disables, uninstalls, and enables the module. See heading on Dependent Modules below for more info.
Many problems simply arise from a missing include in
[myfeature].module. If it does not contain this line, re-add it:
Missing feature module files
Check your codebase
If you are pushing your custom feature modules by using source control, be certain that all required files have been checked in and exist in the problem environment. When updating and downloading features, additional files may be generated that must be added to source control.
Problems with: Views
- View created that has multiple pages which are added within the view as local tasks.
- View added to the feature & exported correctly.
- Enabled the Feature and reverted all components.
- Site cache cleared.
- View still shows as Overridden in admin/build/features but shows as Default in admin/build/views.
- In admin/build/features/myfeature/diff the Default column shows a near-complete export of the view while the Overrides column starts with the following:
'0' => $view = new view;
drush fuon the feature results in no file changes to the feature.
- Another module had implemented hook_views_default_views_alter() and was manually adding new views this way, rather than first verify the new views existed. The solution was to just verify the view existed before loading it.
- See the parent issue for more details.
- bug can also cause something similar.
Problems with: Table Wizard & Migrate
Problems with: Blocks (via fe_block)
Example #1: Check the theme
Original site (local dev perhaps) shows Default state, when staged to remote shows Overridden. Feature contains features_fe fe_block item(s), and features-diff shows a block config with a theme name in it.
Resolution: Enable and disable core themes to match originating environment: fe_blocks captures block settings per-theme.
Problems with: Features namespace change
Feature name-spacing is used throughout a feature's files. If folder names are changed the feature will remain available and enabled but overridden and unable to revert.
Resolution: Change the folder name back to the original name-space found within the files as function names, filenames, etc.
Problems with: Modules' versions changed
Feature was created with earlier version of core/dependency module(s) and some parts of feature will remain overridden. This is usually a case of transferring features between websites, when it is easy to miss modules versions compatibility.
Resolution: Recreate all features that use new core/module(s) version and clear cache.
Problem with: Missing Dependencies
Missing dependencies can be caused by a number of reasons. Common causes are: a) dependent modules were installed since feature was enabled or b)a module requirement for an exportable is not detected.
a) Feature was created with some set of dependent modules, shared, and later an additional module dependency was added. In terms of Feature as a module, this dependency does go into the .info so any new installations/enables of the Feature will work as expected, but for preexisting Feature implementations (dev/staging environment for instance), these dependencies will not automatically become enabled from a feature revert. This is very likely when sharing Features between development environments and Git branching.
b) Features automatically detects ctools exportables and add the modules containing those exportables to the dependency list. However, if a contrib module builds on user entered data (for instance, content_taxonomy on a specific vocabulary), You can export the vocabulary or the term reference field but features doesn't detect content_taxonomy as a requirement. If you don't enable the content_taxonomy module the field will remain overridden and unrevertable. This issue is likely to occur when creating features related to user generated content with extensions on its widgets such as menu links, vocabularies and terms or entities with UUID's.
Resolution:Either disable the Feature and reenable it, or manually enable any dependencies not enabled (see Feature Diff to expose them).
Problem with: Feature with Rules not reverting (in 6.x)
Resolution: Delete all the Rules that are marked as "Custom" status and are also "Overridden" by the Feature. It will change their Rules status to "default" and the Feature will also be "Default" state.
Note: Remove this when that issue is fixed in Rules.
Problem with: Exported translatable strings
With many exportables translatable strings are generated for multilingual sites. These are exported in features.*.inc as
t('english string') calls. However, if you're administrating your site with a different default language than en_US the feature might seem overridden. This is especially prevalent in views exports with translatable labels.
Resolution:Change the administrator account's default language to english or change the current user's session language to english when running a features-diff in the UI or via drush.
Problem with: PHP cache
Remember to clear your PHP cache (e.g. APC) after updating the code and before doing the feature revert.
NOTE: This page is a summary of things raised in issue. It is incomplete — earn yourself some karma points by continuing to transfer relevant situations from that issue. Thanks!