Jump to:
| Project: | Features |
| Version: | 6.x-1.0-beta3 |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | yhahn |
| Status: | closed (won't fix) |
Issue Summary
I searched the queue for a similar issue but did not find one.
I just created a feature using cck 6-2-5 and file/imagfield 6-3-1 (all one version behind the current) and exported it to a site that was up-to-date and got a number of db errors. It was easy for me to realize what was going on and to update to the current versions. But for someone new to Drupal that might be tough to overcome. And if they knew enough to file an issue would be difficult to troubleshoot.
I am thinking that the solution might be to include the version number for the module and show a warning if the module version from the feature export is different than the current site.
I looked around and think that this could be included in the hook_features_api() which could call to a function that looks up the correct version number either through the .info file or CVS/Tag file. A similar lookup could be done on the other end, could be checked against the version number during export, and a warning put on the features menu if items are different.
If you think this is worth tackling I'd be willing to do as much of the grunt work as I could.
Comments
#1
It's been put on the radar. Consulting wise sages about it. Expect word soon.
#2
Drupal 7 has versioned dependencies and the syntax doesn't look like it'll be compatible with D6 (http://drupal.org/node/542202). You're welcome to look into this further, but I don't think this will be something we'll incorporate into Features in the D6.
#3
Makes sense. Glad to hear about D7. Keep up the great work.