When fieldgroups are deleted (= disabled status in ctools), features doesn't see that my feature is overriden.

Comments

mpotter’s picture

mpotter CreditAttribution: mpotter commented
Status: Active » Closed (won't fix)

Closing this for lack of activity. Please re-open this issue if you can reproduce it in the latest version.

nils.destoop’s picture

nils.destoop CreditAttribution: nils.destoop commented
Category: bug » support
Status: Closed (won't fix) » Active

Still got the same with latest dev version. But changing this to a support request.

This is how fieldgroup deletion works:

When a fieldgroup is deleted, we run following code:
ctools_export_crud_disable('field_group', $group->identifier);

Ctools is then setting a variable, that our fieldgroup is disabled. This is the part that does not get noticed by the features as overridden.

Is this something that can be fixed inside features itself, or does fieldgroup needs to add an own hook, that marks as reverted?

Same problem occurs when you delete a fieldgroup. And then enable the feature. The group will still be disabled, until you manually enable the fieldgroup itself.

mpotter’s picture

mpotter CreditAttribution: mpotter commented

What specifically are you exporting in your feature? The fieldgroup itself? Can you post the *.info file for the feature?

nils.destoop’s picture

nils.destoop CreditAttribution: nils.destoop commented

I'm indeed exporting the fieldgroup. An example can be downloaded at http://drupal.org/node/1619154#comment-6397046

mpotter’s picture

mpotter CreditAttribution: mpotter commented

In the field-group issue you linked, somebody reported after your post that installing the latest field-group dev version fixed it for them. Can you try that and report back?

13rac1’s picture

13rac1 CreditAttribution: 13rac1 commented
Version: 7.x-1.0-beta3 » 7.x-1.x-dev

I can confirm the most recent field_group and features dev versions do not fix this issue. Field groups are never marked as overridden. Possibly just for fun, the taxonomy and fields are always shown as overridden.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

This is probably related to (or possibly a duplicate of) #1619154: Fieldgroup exported feature reports as Overridden just after creating the feature, which is reporting problems with fieldgroups and Features as well?