Now when exporting display suite settings as a feature, settings for all node displays are exported.

Since a feature is usually a package of one or more content types (not all) I would expect the ability to select which content type displays I want to have in my feature (like on the export page).

Comments

swentel’s picture

swentel commented
Title: Support feature integration per node type » Support feature integration per object type + more exportables
Project: Node displays » Display Suite
Version: 6.x-2.0 » 6.x-1.x-dev

Makes sense - I need to re-evaluate features integration anyway (more exports eg all variables) - moving to the right queue.

swentel’s picture

swentel commented
Title: Support feature integration per object type + more exportables » Support feature integration per object type

Changing title - jeej for strongarm to export variables :)
Export per feature coming soon.

swentel’s picture

swentel commented

Ok, commited the code - you can now select which object to export to default settings.
Not closing however, because I have 2 small things I need to look at:

- fieldgroups aren't recognized when in code
- revert fields in general, need to find out how to accomplish that (if possible at all)

swentel’s picture

swentel commented

Ok fieldgroups are recognized, you just don't see them at admin/ds/nd/fieldgroups which isn't a problem at all. looking for field defaults now.

swentel’s picture

swentel commented
Status: Active » Closed (fixed)

Ok, fields is really to hard right now to keep track of overridden values - implementing hook_ds_fields in the generated module file by features seems like a better solution anyway, because less code is loaded than. Closing for now.

swentel’s picture

swentel commented

Oh and btw, changing fields from code and seeing the change of it after flushing cache will be solved after #779040: Create DS UI module gets in.

stijndm’s picture

stijndm commented

Allright, checking this out soon.