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.
I just ran drush fl twice in a row, and got 2 different results. Needless to say there were no changes made in between, and this is on my local with no changes coming from anywhere else:
archetypes $drush fl
Name Feature Status State
Archepedia archetype_archepedia Enabled
Archetype Article (& Page) archetype_article Enabled Overridden
Archetype Discover archetype_discover Enabled
Archetype Friends archetype_friends Enabled
Archetypes Me'ing archetype_meing Enabled
Archetype Messages archetype_messages Enabled Overridden
Archetype Search archetype_search Enabled
Archetype User archetype_user Enabled
Date Migration Example date_migrate_example Disabled
archetypes $drush fl
Name Feature Status State
Archepedia archetype_archepedia Enabled
Archetype Article (& Page) archetype_article Enabled Overridden
Archetype Discover archetype_discover Enabled
Archetype Friends archetype_friends Enabled
Archetypes Me'ing archetype_meing Enabled
Archetype Messages archetype_messages Enabled
Archetype Search archetype_search Enabled
Archetype User archetype_user Enabled
Date Migration Example date_migrate_example Disabled
I should add that when this happened I was trying to determine why a feature listed at overridden would not revert (says it reverted, but still shows as overridden.)
Comment | File | Size | Author |
---|---|---|---|
Screen shot 2012-09-26 at 10.58.23 AM.png | 28.24 KB | forestmars |
Comments
Comment #1
Owen Barton CreditAttribution: Owen Barton commentedThe features-list command is part of features module, and this doesn't sound like Drush core is to blame, so changing the project.
Comment #2
forestmars CreditAttribution: forestmars commentedGood call Owen, this definitely seems to be a features, not a drush, bug.
Comment #3
mpotter CreditAttribution: mpotter commentedIf you have a way to reliably reproduce this, please let me know if clearing the Drupal cache first causes the two features lists to be the same. I am not able to make this happen here.