@rhache: That Semantic CCK integrates with Features is really useful and shows that the module has not only style, but also quality. I think that this should be mentioned on the project page.
@Itangalo: Semantic CCK integrates with Features based on the fact that we're storing our settings in the same place that CCK itself stores it's field settings. This may have to change in future versions of Semantic CCK (see: #857602: Parameter 3 to semantic_cck_field_settings_alter() expected to be a reference), but we'll accept the compliment anyways :)
I'm going to assign this issue to myself to investigate features integration a little further before we post anything about that on the project page.
Comments
Comment #1
itangalo commentedYes it does!
However, Features doesn't (yet) recognise the dependency on Semantic CCK so you must add this manually.
Comment #2
itangalo commentedComment #3
itangalo commented@rhache: That Semantic CCK integrates with Features is really useful and shows that the module has not only style, but also quality. I think that this should be mentioned on the project page.
Comment #4
dasjogreat aspect, like it
Comment #5
rjay commented@Itangalo: Semantic CCK integrates with Features based on the fact that we're storing our settings in the same place that CCK itself stores it's field settings. This may have to change in future versions of Semantic CCK (see: #857602: Parameter 3 to semantic_cck_field_settings_alter() expected to be a reference), but we'll accept the compliment anyways :)
I'm going to assign this issue to myself to investigate features integration a little further before we post anything about that on the project page.
Comment #6
rjay commentedI've implemented one of the features hooks to automatically add Semantic CCK as a dependency when adding fields to a feature. Committed to 6.x-1.x.