Right now when you export a taxonomy vocabulary as part of a feature, the 'hierarchy' is exported as part of it. This represents the depth of all the terms currently on that vocabulary. It will result in the feature being overridden if an end-user adds or removes a level of child terms.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

cboyden created an issue. See original summary.

cboyden’s picture

Status: Active » Needs work
FileSize
345 bytes

Here's a patch that looks like it should do the right thing, but doesn't seem to be having any effect.

dsnopek’s picture

Title: Features should ignore the term depth of a taxonomy » Features should ignore the 'heirarchy' key on a taxonomy
Issue summary: View changes
Status: Needs work » Reviewed & tested by the community

The patch worked for me with the latest version of Features!

I suspect you're using a version of Features before this commit was made:

http://cgit.drupalcode.org/features/diff/features.export.inc?id=7c288b13...

cboyden’s picture

Yes, thanks @dsnopek, that was the problem!

cboyden’s picture

Title: Features should ignore the 'heirarchy' key on a taxonomy » Features should ignore the 'hierarchy' key on a taxonomy
cboyden’s picture

Issue summary: View changes

  • mpotter committed 095ee1b on 7.x-2.x authored by cboyden
    Issue #2604554 by cboyden: Features should ignore the 'hierarchy' key on...
mpotter’s picture

Status: Reviewed & tested by the community » Fixed

Committed to 095ee1b.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.