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.
Try this with this feature: http://waterfall.features.bkstg.artistarena.com/node/1.
Enable the feature. Make some changes to say one of the views. Then revert all the features. The flag component won't go to default status unless you go disable the flag itself.
If this is by design please explain. I am coming from the point of view that I want my features to be in their default state all the time to simplify deployment.
Thanks for the great module! Love it
Comments
Comment #1
ghankstef CreditAttribution: ghankstef commentedOK after digging into this some more, I see that my flag features configuration has code like this in it:
And commenting these out as about allows me to revert the feature. Hooray! I suspect that this ma be an artifact of updating from flag 1.x to 2.x but I'm not certain on that.
Comment #2
xtfer CreditAttribution: xtfer commentedIm seeing the same issue, but there is no commented code in the export.
As viewed with the diff module, the features faux export doesn't appear to have the flag name in it, thus triggering the overridden state. Otherwise it seems to be up to date.
Comment #3
lpalgarvio CreditAttribution: lpalgarvio commentedi'm using 6.x-2.0-beta5
Comment #4
joachim CreditAttribution: joachim commentedNeeds checking on 3.x.
Comment #5
joachim CreditAttribution: joachim commentedWorks fine for me on 7.x-3.x.
Can someone try this out on 7.x-2.x?
Comment #6
joachim CreditAttribution: joachim commentedThis is a deeper problem: there is no way to revert a flag to code, whether that is to undo UI customizations, or cause changed to the code to be reflected in the flag.
I think we're too far in 3.x to tackle this in clean ways (such as changing Flags to be CTools plugins).
However, I'm open to fixes for this that don't make huge structural changes to the code.