Why would some features still show as "Overridden" even after running a full features revert with the force switch? Below are the commands I am running, for the sake of clarity.
drush fr-all --force -y
drush fl
asked Mar 6, 2011 at 19:11
-
There is a whole thread over on d.o with lots of information about this. drupal.org/node/744450 There are quite a lot of reasons why it would. It's quite an open ended question.– digitalMar 7, 2011 at 18:27
Add a comment
|
5 Answers
A feature or features may not revert for the following reasons as cited by some developers in the issue queue #744450:
- If your feature includes a view views cache could cause it to remain changed; especially, the migrate module (#1)
- Other features can cause your feature to be overridden (#10)
- Adding a line in your info file (#24)
- There are hooks overriding or altering your view (#36)
- A view won't revert. So revert the view using the UI (#62)
- When Views UI is disabled, it may cause your view to be overriden (#64)
- A feature is missing an include file (#82)
answered Apr 18, 2013 at 15:26
One way of that happening, that I've tried myself, is to have two seperatere features define content types that use the same CCK field. Doing that it's possible to have different settings for the same field for. That way one them will always be overridden.
answered Mar 6, 2011 at 22:09
There is more documentation related (https://www.drupal.org/node/986932), including a description of a silver bullet solution (Disable and re-enable. be careful and test first).
Here's a known issue, http://drupal.org/node/860974
I am battling that one myself.
It does depend on what you are trying to override. The output of drush features-diff could be helpful for others to give you a more precise reason.
This may seem stupid, but make sure you have all the files for the feature. One of my files didn't make it to git so it kept showing overridden.
