You should be able to do this if you’re using the Validation service. Here’s some docs on conditionally-required fields. And if you need more control, there’s Custom Conditional Rules.
I’m not sure if we’re talking about the same thing or not. I mean all fieldtypes for an entry in general. I’m talking higher level than validating fields in my own custom field type. I mean as I’m laying out channel entires as a general developer in ExpressionEngine and designing the content structure. There may be some fields that I need to require along with others, and some fields I don’t want to require if another field is filled in.
Oh, I probably did mention it, I just didn’t have the hard drive space to store that particular bit apparently. I’ve wished it could be done before. It came up again today and I thought why not post it where it can get some attention.
I do remember discussing that when fieldtypes are decoupled from field groups whether they are required or not would need to be a setting when adding them to a channel, and not always for that field. So my mind is not completely gone. 🐛
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.