Adding export Features for DDF

What did you mean?

Hi Max,

I'm experiencing the same issue. It seems like ddf settings are not exportable through Features module.
Do you have plans to implement Features module support?

Thanks,
Konstantin

They are normal field settings. Why won't they be exported?

Oh, no, I forget about the additional settings stored in the DB. Could someone provide the patch for this?

Hi Max,

Please give us an idea which setting exactly we need to save additionally.

Thanks,
Konstantin

Oh, I've found it, the ddf table contains necessary settings.

The following code will add necessary setting to the database:

  $settings = array(
    'type' => 'options'
  );

  $fields = array(
    'field_name' => 'field_1',
    'entity_type' => 'node',
    'bundle' => 'article',
    'dependent_field_name' => 'field_2',
    'data' => serialize($settings),
  );

  db_insert('ddf')
    ->fields($fields)
    ->execute();

I've added this code to my hook_update_N as a workaround.

Hi,

Here is one patch me make DDF features exportable.

Path for retest

Oh!
Different folder.

@yuriseki
Advanced patch contributor guide may help.
Also, make sure the number (N) in hook_update_N is correct.

Thanks Konstantin,

I followed the guide, hope it works this time :-)

Thanks for the patch. Just a couple of little issues with #17

• specifies the unique key incorrectly in hook_schema
• DDF tablename shouldn't be capitalized

Fixed patch attached.

On a clean install with a ddf field in a feature, the dynamic field doesn't update properly. Saving the field settings fixes it. It seems that the feature revert isn't saving the settings to the db? It could also be that it uses a field id to target ddf, which can be different depending on when features are enabled.

Ah, good catch mortona2k...I didn't look at this carefully. Needed to refactor ddf to use a consistent load function and use Ctools to load our exportables. Patch attached.

Maybe it's better to get rid of a dedicated DB table and just store the ddf settings in field instance settings.

Maxim, in that case we'd need an upgrade mechanism.

I agree with #25. Storing the settings in field instance settings will make the export more robust.

/Leiph