I originally assumed that the plugin is designed to have one or more child custom fields that are dependent on a parent custom field.
For example:
- Parent
- Child1 that has values dependent on Parent
- Child2 that has values dependent of Parent.
However, it seems that the plugin is designed to config the Parent -> Child relationship and save this under the parent. That is unfortunate, since it is a more limited design that assume 1 Parent controls 1 Child custom field.
It may be too late to fix that, but at least we should use terminology "Parent Custom Field" and "Child Custom Field" instead of "Custom Field" and "Linked Custom Field", since the latter is ambiguous and can be confusing.
I originally assumed that the plugin is designed to have one or more child custom fields that are dependent on a parent custom field.
For example:
However, it seems that the plugin is designed to config the Parent -> Child relationship and save this under the parent. That is unfortunate, since it is a more limited design that assume 1 Parent controls 1 Child custom field.
It may be too late to fix that, but at least we should use terminology "Parent Custom Field" and "Child Custom Field" instead of "Custom Field" and "Linked Custom Field", since the latter is ambiguous and can be confusing.