Closed (fixed)
Project:
Features Extra
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
9 Nov 2010 at 18:47 UTC
Updated:
2 Feb 2013 at 17:10 UTC
The actual Features module: http://drupal.org/project/features now includes support for taxonomies. Features extra taxonomy support is duplicate. Is there a reason to keep it?
Comments
Comment #1
wizonesolutionsSounds reasonable...I think this module was just intended to provide stuff Features didn't. Maintainership of this module should go to me or someone else soon, so we can look into it.
Are there any fundamental differences between the taxonomy support in the two or does Features do it the exact same or better than Features Extra? Also, I think we would need a migration path from people who depend on fe_taxonomy so that they can somehow migrate their featurized taxonomies into the way Features does it. Patches welcome.
I've never actually never enabled fe_taxonomy, so I wonder if we need to remove it or if we could just put a note on the project page saying, "The Features module is already capable of managing Taxonomy Vocabularies, but have retained the fe_taxonomy module for backwards compatibility. It may be removed in a future release. If you don't already have feature modules depending on fe_taxonomy, we recommend leaving it disabled.
Then we could do the whole remove it/migration path thing in a 2.x branch release, or in Drupal 7 if applicable. What do you think?
Comment #2
toleillo commentedTaxonomy support removed from 7.x version.
Comment #3
rogical commentedFE taxonomy can't be found in the features module, and features can't export terms, only vocabularies.
Comment #4
henrijs.seso commentedWait? What? Features can not export terms. FE Taxonomy could (I think). Too soon!
Comment #5
hekele commentedPlease add FE Taxonomy again to features extra. You can't export terms with basic features module.
Comment #6
mautumn commentedYes - "Please add FE Taxonomy again to features extra. You can't export terms with basic features module."
Often one or more taxonomy vocabularies and their terms are required to achieve some functionality in a Feature - like methods of payment or days of the week in an event reservation feature - and so packaging them with the Feature is the most logical place to export/import them. The alternative is to export and import separately after installing the necessary modules, and it just means more unnecessary work on the sites using the exported feature.
The case can be esaily made that taxonomy vocabulary terms should be included in the main Features module, however, given that this functionality was switched off in this module - in the mistaken belief that it was duplicated functionality - then presumably switching it back on would be considerably less work than adding this functionality into the main Features module...
Pretty PLEASE! :)
Comment #7
dbhamel commentedYes, I agree. For now, it would seem the FE taxonomy that use to be in features extra is exactly what I needed. I wrapped content types and the related taxonomy in a feature but the vocabulary terms within each vocabulary did NOT come through. Would have liked to try it out or hope to see the same functionality in Features soon.
Comment #8
papirrin commentedSame here, Features module does not export vocabulary within features and I'd like to have this functionality.
Thanks!
Comment #9
sheldon rampton commentedFYI, the UUID module and UUID Features module provide a way to export vocabulary and terms:
http://drupal.org/project/uuid
http://drupal.org/project/uuid_features
Comment #10
pfrenssenIf this is possible using UUID Features I guess it is not necessary that Features Extra duplicates this functionality. I'll add a message to the project page so people are aware this can be done with UUID Features.
Comment #11
pfrenssenThe original task has already been completed almost 2 years ago, setting this to fixed :)