Conversation
Notices
-
@freemjd: What's the cause/fix for #Features that say 'overridden' or 'needs review' as soon as you enable them? !drupal
about a year ago from pino-
@bwpanda Pretty much every setting except Views needs to be reverted if it's different to the db state when you install/upgrade a Feature.
-
@bwpanda `drush fd [feature name]` will tell you what you're about to change when you do `drush fr [feature name]`.
-
@bwpanda Screwy use of the term 'revert', since you're almost certainly changing the config to a state it's never been in before...
-
@bwpanda Views is the exception, since Features is just leveraging the mechanism Views has had for ages for modules to define default views.
-
@mjd Yeah, but even after reverting it still says Overridden...
-
@bwpanda Oh, in that case clear the cache several times before giving up.
-
@bwpanda Loads of times I've had Features reported by `drush fl` as overriden, but `drush fd` says 'Feature is in it's default state..."
-
@mjd 'drush fd' lists my features and says that packweb_core is enabled and overridden. 'drush fd packweb_core says 'No diff needed.'
-
@bwpanda Yes, just one of those screwy glitches. Often the web UI features overview and `drush fl` disagree as well.
-
@bwpanda If any 1 source says the Feature is in it's default state, and none can tell me how it differs, I assume it's in sync with the db.
-
@mjd Hmm, reverting feature makes my Nav menu display expanded as expected, but clearing cache shows it hidden and feature saying overridden
-
@mjd Settings aren't sticking for some reason...
-
@bwpanda There's a bug with exporting multiple menu items with the same path that's caught me several times: http://drupal.org/node/927566
-
@bwpanda If you need to work around it, you can always do a hook_menu() or hook_menu_alter() in the Feature's .module file, I suppose.
-