Probably a bad idea to set a NodeType to «abstract» when already Nodes are created from this type. Could be, this setting is responsible not only new creating elements, but also already created ones … And then those will cry, because those are obvious more than from abstract-nature.
Did a search-replace in Database for old Neos.NodeType:Text/Headline and replace it with new one, extended from the default nodeTypes.
For sure the lumberjack method, but it works -> No errors left.
@martoro: I’m on the right track?
####What does not fit with the idea[quote=“martoro, post:4, topic:2173”]
stumble upon a nodeType Vendor.Site:Headline i will instantly know that this is no default type
Maybe it’s something with conjunction to Demo.Site. But at the end I can use new ones without confusing multiple choice for each type and without Error-Throwing. On other (new) Projects, there will be no default Neos.NodeType:Text and Headlines in DB. So no Error from beginning.
Would be a better solution if I could also use in past projects, but maybe this is the borderline …