AFAIK if a part (in this specific scenario, an empty part, without a record and even without properties) is attached to a type, it'll be listed in ContentItem.Parts as its own type. E. g. if a part (ContentPart child class) is attached in the migrations
with its name, say, "MyPart", ContentItem.Parts will contain an object of type MyPart. Now I tried to add a new part to a type, it gets added but it's stored as ContentPart in the Parts list. This is the same as when a part is not created from
a class, but in migrations (like welding fields together).
However there is another part that works, used the same way. This works:
cfg => cfg
public class MyWorkingPart : ContentPart
But this doesn't:
cfg => cfg
Can you see a difference?
public class MyNotWorkingPart : ContentPart
Even if I try to attach the two parts to the same type (new type, even the installation is a wipe-out, so there should be really no difference), the same works and the same doesn't. Heck
even if I copy-paste the working part, modify one letter in its name and try to attach both to the same type it shows the same failure. What kind of sorcery is this?
Any help would be really appreciated (not how to solve this, as I guess from this there can't a solution be deciphered but for a direction where I can start to investigate the problem) as I can't think of anything to solve this.