I'm not 100% sure how to deal with this one but the display formatters for hidden displays retain the fieldfield and imagefield module settings when they are migrated using content_migrate. It's not really an issue for the fields module until you try and export those fields using Features where upon Features tries to list fielfield and imagefield ass dependencies (obvioulsy bad as those are D6 modules). I believe this is what is causing this issue http://drupal.org/node/1306240.

Patch attached in next comment, again I'm not 100% sure my patch is the best way to do this. I'm not 100% sure these display formatters should simply be using the default. It could be the issue that Features isn't respecting the "default" display concept.

BTW, sorry if I got the component wrong in the settings, I wasn't 100% as there is no choice for content_migrate as a module

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bigjim’s picture

Status: Active » Needs review
FileSize
1.35 KB
bigjim’s picture

I forgot this is also true for optionwidgets, new patch attached

zeisllo’s picture

Adding patch for text and number fields.

Senpai’s picture

I was gonna say that patch #3 doesn't work, until I realized (after several hours of testing) that patch #1 and #2 also have to be applied. They don't build on themselves.

Back to patching and testing this...

Senpai’s picture

Status: Needs review » Reviewed & tested by the community

All patches apply, but they don't apply from the same place. To use #1 and #2, put the patch into the CCK module and then apply it. To use #3, place the patch into the root of your Drupal site, and pray that you have your contrib modules inside of a contrib/ subdirectory. :)

All patches apply cleanly, and they seem to work as intended. Thanks for the effort, @jalama and @zeisllo!

Senpai’s picture

Followup to my own followup. I just diffed patch #1 and #2 against each other for fun, and patch #2 contains all of patch #1's changes, so if you're testing this, you really don't need to bother applying #1. Just use #2 and #3.

bigjim’s picture

#2 & #3 (and of course #1) re-rolled here as one patch.

yched’s picture

Status: Reviewed & tested by the community » Fixed
FileSize
2.21 KB

I'd say this should to fix this for all field types ?
Committed the attached patch.

Status: Fixed » Closed (fixed)

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