Forgive is this is a sore topic. I searched the queue and did not find anything related to this.

I have been using features heavily lately and many times the features are large, requiring multiple modules. When I moved the features over to the demo server I ran into several issues related to modules not found within one of the dependencies. It turns out, the modules versions I used on my localhost did not match what was on the demo server. It seems that when enabling the feature via drush, drush will download the stable version of the module that is required.

For example, both uuid and references have sub modules only in specific versions of the modules... Drush downloads the stable version and uuid_path submodule is not available to enable, so features break.

Is there a way to speck out the version of the module dependency in the file?



jastraat’s picture

I believe Drupal 7 allows you to specify a version in the dependency information in the .info file.
dependencies[] = mymodule (1.0)

See the section on dependencies in

elvis2’s picture

@jastraat thank you for pointing that out!

ram4nd’s picture

Does features support this?

jastraat’s picture

I believe so; they are modules as well. Not sure it's possible to specify in the user interface though.

ram4nd’s picture

I don't think features adds version numbers for dependencies, maybe it should be an option. Maybe it should be a feature request.

mpotter’s picture

Category: bug » feature
waako’s picture

Issue summary: View changes

The main issue is that when you recreate a feature it overwrites any version you have specified manually in the .info file.

hefox’s picture

Title: features and module version dependencies » Allow specifying module dependency version for a feature

trying to clarify title

Dane Powell’s picture

Additionally, if you specify a versioned dependency in a feature right now, it shows as perpetually overridden. I think that should qualify this as a bug.