Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When running features-revert-all I get "Command features-revert-all needs the following module(s) enabled to run: features." even though features is active on my site. See enclosed image.
Comment | File | Size | Author |
---|---|---|---|
Screen Shot 2012-10-24 at 4.11.01 PM.png | 38.61 KB | alberto56 |
Comments
Comment #1
pvhee CreditAttribution: pvhee commentedSame issue here. Seems randomly,and sometimes clear cache solves the problem.
Comment #2
mpotter CreditAttribution: mpotter commentedWas not able to reproduce this at all. What changes are you making to your site when you do this? As mentioned in #1 if it's a fresh install you probably need to clear cache so Drupal can find the modules that are installed before you revert your features.
Comment #3
michaelmallett CreditAttribution: michaelmallett commentedI often get this, I clear the caches and it generally tends to work. This, however causes a few issues if I have a field change or some other feature conflict
Comment #4
gaas CreditAttribution: gaas commentedI see this quite often as well. If I run:
it does not fail. If I run:
It fails even if
drush updb
appears to do nothing. The failure looks like:Adding another '
drush cc all
' between the 'updb
' and 'features-revert-all
' helps.Comment #5
alberto56 CreditAttribution: alberto56 commentedInteresting, thanks. I have tried to reproduce this but for now it seems to be really intermittent. If someone finds a consistent way to reproduce, please reopen the issue.
Comment #6
treksler CreditAttribution: treksler commentedcan reproduce
ran updb via drush on all sites
after that features-revert-revert-all fails
Command features-revert-all needs the following module(s) enabled to [error]
run: features.
Comment #7
treksler CreditAttribution: treksler commentedfor what it's worth, the database update added a column to one of the tables in the database
cc all does allow the features revert to proceed
Comment #8
treksler CreditAttribution: treksler commentedproblem is even worse
ran updb via drush on all sites
afterwards i get the following errors until i clear cache
this can happen if the hook_system_info_alter does not fire when rebuilding theme and module data
basically updb leaves the theme and the module registry in a broken state
this might be a bug in drush actually
Comment #9
treksler CreditAttribution: treksler commentedi believe this is actually caused by https://drupal.org/node/602182 which will be fixed in drush 5.10 whenever it comes out
if anyone is having issues, try with the latest drush from git and report back
cheers
Comment #10
hefox CreditAttribution: hefox commentedI cannot fathom that this is a features bug, and since treksler linked to a drush issue, marking this as closed
Comment #11
JohnAlbinThe drush bug mentioned in #9 was committed and pushed to 5.x and 6.x. However, with Drush 6.1, I'm still seeing this error.
I'm not trying to play the blame game, but this issue should be reopened until we can figure out where the bug lies.
Here's what I'm seeing:
If I revert the features individually (instead of with fra) by doing
drush cc drush
and thendrush fr feature_1
, the feature is reverted successfully. But I have to run drush cc drush before doing any feature command.Here's the related issue in the Drush queue: https://github.com/drush-ops/drush/issues/73
Comment #12
fullerja CreditAttribution: fullerja commentedI am also seeing this behavior with Drush 6.1. I get it with
drush fr
, as well asdrush fra
Comment #13
BarisW CreditAttribution: BarisW commentedSamen here with drush 6.1.0. Also with
drush fd
.Comment #14
hefox CreditAttribution: hefox commentedPlease see drush issue queue. There may be something with with features drush integration, but not from what I've seen -- the error just doesn't make sense.
My guess it's features intergration commonly seeing it because of when features tends to be run (after updates, etc.).
Comment #15
BarisW CreditAttribution: BarisW commentedHere's the issue in the Drush issue queue: https://github.com/drush-ops/drush/issues/79
Comment #16
nategasser CreditAttribution: nategasser commentedI see this from time to time and so far I've always been able to clear it up with either a "drush cc all" or a "drush updatedb"
Comment #17
geerlingguy CreditAttribution: geerlingguy commentedDitto all the above comments; if I run
drush cc all
when I get this notification, then re-runfra
, it works. Annoying, but thought I'd give another +1 here, since this is about the fifth time my googling has brought me here :PComment #18
dkinzer CreditAttribution: dkinzer as a volunteer and commentedUpdate: my issue had nothing to do with this issue.
Not 100% sure this is related, but I ran drush fra and drush fr via a dugger and noticed that `hook_fielb_base_alter` is run after `hook_field_base` when using the single option, but when using `fra` it's the other way around (which of course doesn't make sense).Comment #19
nicholasruunu CreditAttribution: nicholasruunu commentedYeah, just had the same issue, drush cc all fixes the problem.
Comment #20
kenorb CreditAttribution: kenorb commentedThe same here.
This may be drush issue: https://github.com/drush-ops/drush/issues/79
Comment #21
rwam CreditAttribution: rwam commentedPuh, we ran into the same problem with Drupal 8.5.4, Features 8.x-3.7 and Drush 8.1.14. Annoying.
Doesn't work:
Work:
Comment #22
kenorb CreditAttribution: kenorb commented@rwam Your problem is completely different with different major version. I've created an issue here: #2986328: Current state already matches active config, aborting.