Fields dependency
Last updated
Last updated
This option serves to define the dependency of different fields. It shows the connections of various fields and indicates the changes in the values of options.
It’s critical to understand the work of the dependencies. Let's break the process down with an example.
The fields won’t be displayed unless a particular setting is enabled or selected.
For example, there is a field for skin color setup. By default, the theme color are applied and there are no additional settings. But if you select the Custom Color option, the new fields (color picker) will be displayed. These fields depend on the Custom Color option.
The 'value' => 'not_empty' indicates that if the setting is enabled, the field will be displayed.
2. Another example of dependency usage. There are three option fields, two of them depend on the third one. When you select Hide Footer (enable the option) other two settings will be automatically disabled and hidden.
The 'value' => 'empty'
indicates that if the setting is disabled (or not selected) the field won’t be displayed
3. There is also another way of dependency management when some of the fields depend on two options at once.