PHP Notice: undefined index when migrating decimal number

I have a similar problem. i upgraded a website from d6 to d7 with 2 custom fields. one was a text field and was imported with no errors but I cant get my field "decimal number" to get imported. It stopped with an error "... AJAX HTTP. HTTP Result Code: 500 ... Internal Server Error ResponseText:"

The field ends up under "converted fields" but is not listed under its node types "manage fields" nor by viewing or editing a node supposed to have this field.

Here some log messages:
Notice: Undefined index: module in _field_write_instance() (line 600 of .../modules/field/field.crud.inc).
Notice: Undefined index: inline in content_migrate_number_instance_alter() (line 148 of .../sites/all/modules/cck/modules/content_migrate/modules/content_migrate.number.inc).
Notice: Undefined index: inline in content_migrate_number_instance_alter() (line 147 of .../sites/all/modules/cck/modules/content_migrate/modules/content_migrate.number.inc).
Notice: Undefined index: image in content_migrate_get_options() (line 37 of .../sites/all/modules/cck/modules/content_migrate/includes/content_migrate.admin.inc).
Notice: Undefined index: inline in content_migrate_number_instance_alter() (line 148 of .../sites/all/modules/cck/modules/content_migrate/modules/content_migrate.number.inc).
Notice: Undefined index: inline in content_migrate_number_instance_alter() (line 147 of .../sites/all/modules/cck/modules/content_migrate/modules/content_migrate.number.inc).

any help appreciated! THX.

Subscribing

subscribing - same problem

drupal 7.0
Content Construction Kit (CCK) 7.x-2.x-dev (2011-feb.-25)
Field converter 7.x-1.x-dev (2011-feb.-25)

Thanks !!

I hit the same bug. The problem is that it's treating the label setting as if it was a whole display type. Here's the patch. It's a tiny change, so it probably doesn't make as much sense if you just look at the patch, but if you apply it and inspect the surrounding code, it should be clearer. I'm not 100% positive this is correct -- I barely understand the D7 field API at this point. But, this seemed to solve this particular upgrade problem for me. Thoughts from KarenS most welcome! ;)

The patch seems appropriate to me, but haven't had an opportunity to test it yet.

Looks right, committed. Thanks!