How can I export the configuration of pseudo fields as set from the display configuration for my entities types and their bundles ? When exporting a normal fields instance (with Features) its display settings, for each available view mode, are exported with it. But I cannot find how to export the settings for the pseudo fields such as the History field of a User entity and the File field for a File entity.
4
-
Pseudo fields isn't quite the right term for that but I'm having a hard time coming up with the right one.– drewishDec 2, 2011 at 14:33
-
Ah, well core seems to call them "Non-field elements" which isn't super descriptive. Actually I'm wrong, they're also referred to as pseudo-fields. Learned something new.– drewishDec 2, 2011 at 14:42
-
Does your feature export the content type? It seems like that additional field info is exported on nodes that are "owned" by a feature.– drewishDec 2, 2011 at 14:49
-
No, the feature-module does export the content type. It depends on several content-type defining modules and configure them to provide a coherent user experience (same fields ordering on edit and view, same image styles, etc.)– Pierre BuyleDec 3, 2011 at 19:18
Add a comment
|
2 Answers
Strongarm will do this because field_bundle_settings() stores the settings in a huge variable called field_bundle_settings. There is a patch to move it into several variables, but it'll be variables nonetheless.
Edit: I guess the core source code counts as "official source", doesn't it?
-
1FYI, the variable is now split up - e.g. field_bundle_settings_user__user (field_bundle_settings_[entity_type]__[bundle]) Jul 4, 2013 at 13:45
Have you tried Display Suite? It allows for that and much more. It might be overkill, but it just solves your issue AND is exportable in features.
See mortendk post on Display Suite, particularly his slides.
answered Dec 8, 2011 at 16:32
