I followed these steps...

  • I had an existing feature and I added code to the .module file to define a field formatter.
  • I changed on of the field displays attached to a content type defined by this feature to use my new formatter.
  • I went to structure->features and used the "generate feature" function to recreate the feature
  • I saw this: Screenshot_6_26_13_9_40_PM.png

Now if I disable the module I cannot enable it again because there is a circular dependency

CommentFileSizeAuthor
Screenshot_6_26_13_9_40_PM.png87.88 KBbleen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hefox’s picture

hefox CreditAttribution: hefox commented
Priority: Critical » Normal
Status: Active » Postponed

When setting issue priority, don't use priority to yourself, use priority in reflect for the project. Does this effect many users of the module? Does this prevent using the module (e.g. features) Misusing critical priority is a quick way to annoy a module maintainer XD

Did you add a permission that module defined? If so, there's already a bug report on that, mark this as duplicate.

If not, that existing issue will likely fix this also, so leave this postponed.

Till they, since you're using the 2.x version, just uncheck the dependency in the ui or manually change it to a features_exclude (format: features_exclude[component type][item] = item)