Dynamic required fields in Content Manager, based on other fields’ options
A
Andreas Oikonomou
Hi! It would be nice and useful to have the ability to make some fields dynamic when writing content, based on other fields.
E.g. a recipe blog with 2 content-types Main Categories and Recipes. Each Recipe has only one Main Category.
The 2 main categories are Food and Beverage.
In the Recipes content-type there is a field called Portions to note how many portions the ingredients of the recipe are for. If the main category selected is Food then we would make the Portions field required. If Beverage is the main category selected then Portions field as is not required.
If we had “dynamic” required fields in content manager, we could make the Portions field on the Recipes required or not, based on the Main Category that is selected, in order to help content creators not miss anything required/important.
Just thinking freely, it would be interesting to have the UI change depending on the selected main category (or some other field). To show/hide basically different fields for food recipes and different fields for beverages, keeping only a handful of shared basic fields like for example, name, slug etc.
P.S. my idea is for content-types that have a few fields different from each other. In my recipes 9 out of 10 fields would be the same and only Portions fields would change. If there are more differences I don't believe this feature would be useful. Creating different content-types would be more logical.