Hello,
it appears that SEBLOD requires the name of a field added to a Content-Type to be globally unique, even if the field is locked to the Content-Type.
However, when I create a copy of a Content-Type using the "batch" copy feature, all fields in the new Content-Type have the same name as in the original. In fact, they appear to be the same (i.e., identical) fields, since (a) they are listed only once in the field manager, and (b) changing one of these fields in one Content-Type simultaneously affects its twin in the other.
Is this the expected behavior? If so, then why is it not possible to reuse a field locked to one Content-Type in another while constructing the Content-Type manually? That would be a very useful feature, since I have several not-so-simple field definitions, e.g, checkboxes with many options that have always been tedious to manually define anew in another Content-Type after I needed a field previously created in an Content-Type again in another one.
In any case, why does a field with locked storage need to have a globally unique name? Is this expected behavior? It is somewhat awkward having to reinvent new names for conceptually the same thing like "headline" or "name" for every new Content-Type. In in addition to that, it also makes code-reuse in a set of custom templates more difficult.
Did I miss something?
Best regards
Stefan