as subject.

Comments

itangalo’s picture

Yes it does!
However, Features doesn't (yet) recognise the dependency on Semantic CCK so you must add this manually.

itangalo’s picture

Assigned: Unassigned » itangalo
Status: Active » Closed (fixed)
itangalo’s picture

Category: support » task
Status: Closed (fixed) » Needs review

@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.

dasjo’s picture

great aspect, like it

rjay’s picture

Assigned: itangalo » rjay
Status: Needs review » Needs work

@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.

rjay’s picture

Version: 6.x-1.1 » 6.x-1.x-dev
Status: Needs work » Fixed

I'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.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.