When exporting a content type in a feature, in this case one that was updated from Features v1, Features v2 has stopped automatically including the fields configured for the associated comment system.

Comments

hefox’s picture

hefox commented
Status: Active » Postponed

Are you sure it ever did and that it was features core itself providing that functionality?

      $fields = field_info_instances('node', $type);
      foreach ($fields as $name => $field) {
        $pipe['field_instance'][] = "node-{$field['bundle']}-{$field['field_name']}";
      }

is the only field instance suggestion for node module. It would have been added for d7 and don't recall ever seeing an issue to add it to d7.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

I didn't create the feature originally so I don't know whether they were automatically selected. However, when the feature was updated they were removed.

It seems like this is two issues wrapped into one:

  • Comment settings should be bundled with content type.
  • Fields are being dropped when the feature is updated with the new field export architecture.
hefox’s picture

hefox commented

The field instance is already covered by that other issue, yea? Autoadding comment fields to content type is a feature request, and one I'm not a fan of as doesn't seem like something that should be autobundled by features core me.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: Comment fields not automatically bundled with a content type » Comment specifications should be automatically included when a node is exported
Version: 7.x-2.0-rc1 » 7.x-2.x-dev
Component: Field » User interface
Category: bug » feature

Refocusing the issue.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Postponed » Active

The reason I believe this should be automatic is that IMHO most people would expect it, and anyone who doesn't want it to work like this can easily disable it, just like what happens with taxonomy reference fields, etc.

vulfox’s picture

vulfox commented
Issue summary: View changes

So I understand this is the right issue..

Export a content type and then deploy it on the target site --> the configured fields for the comments of a certain content type are not there - Right?

I also think this should be a feature of feature.

Is there any way btw to export those fields assigned to a comment of a content type?