fieldgroups? inheriting fields?

[bernhard]

hi,

today i found this screen that was totally new for me after importing a template via import/export tool:

is this because of this part in the export json: "childTemplates":["catalog"], ?

never read about "fieldgroups" concept. any links for me to read? i don't know how i did that - i only did the import ^^ so how would i create such a template manually?

thank you

[tpr]

http://www.flamingruby.com/blog/anatomy-of-fields-in-processwire/

 

In ProcessWire each page implements one template, each template has one fieldgroup attached to it and each fieldgroup consists of varying amount of fields.

Fieldgroup isn't usually something user needs to worry about. Sure, this level exists and is necessary for certain tasks, but it's mostly used behind the scenes by ProessWire itself. What users do see often and should worry about are pages, templates and fields.

 

[bernhard]

thanks tpr, but that doesn't help me a lot...

why am i seeing this list of fields under the "basics" tab and not the standard interface for adding/deleting fields?

[tpr]

It is the first time I exported-imported fields so my findings may be inaccurate. 

The "catalog" text next to the "catalogtest" is indicating that the template is using the same fieldgroup as "catalog" template. That's what is says too ("This template gets it's fields fromt he catalog template"). So they are just "read-only".

When importing, change the name of "fieldgroups_id" in the json, then a new fieldgroup will be created and fields attached to it. At least it worked so here.

[bernhard]

for reference: https://processwire.com/talk/topic/10470-virtual-template/