content type not listed on 5.3

• New Content type + New Field = Works
• Old Content type + New Field = Not Works
• New Content type + Old Field = Works

I try this in different sites onto two multisite installation, two different servers and 5.2 / 5.3 Drupal codebase, but all results are still maddening.

Trying to force $types['image_ncck']['TYPE_ID']['FIELD_ID'] = TRUE; in
emfield.module make the content type visible in the list, permits parsing, but when it imports set it returns a "Cannot access empty property [...] on line 532".

Any idea of what going wrong? There's a method to restore normal module functions without removing the content type or the field?

Brutally solved putting in emfield.module the following lines:

             if ($field_types[$field['type']]['module'] == $module) {
               // settings per content type per module
               $types[$module][$content_type][$field_type] = $field;
+		if(($content_type = "foto") && ($field_type = "field_foto") &&  ($module = "image_ncck")){
+			$store_the_field = $field;
+
+		}
             }
           }
         }
       }
     }
   }
-
+# BRUTE FORCE PASS
+  $types['image_ncck']['foto']['field_foto'] = $store_the_field;
   cache_set('emfield_implement_types', 'cache', serialize($types), CACHE_PERMANENT);
   return $types;
 }

Where:

• $content_type = "foto"
• $field_type = "field_foto"
• $module = "image_ncck"

Before do that, I set also the widget_settings field on node_field_instance to a:0:{} to reset to default the widget settings.

Since the "autodetection" fails for some old fields, before detection is repaired an override function should be implemented.

The import module is great but now is also not well documented, and I found the code quite obscure (but perhaps this is a fault of mine). Please take care of this issue and try to solve it.