Search the Community
Showing results for tags 'required'.
Found 4 results
-
I think this could be a bug. I'm using an Options field to create an array of radio fields. This field is required. Each option activates a conditional field and this works perfectly. I added a required if condition to this conditional fields, on a template level, and this is displayed correctly with the red *. But the fields are not validated and the page saves nonetheless. I figured since the red asterisk is on, I've configured the fields conditions correctly, right?
-
I think that is very useful to set mandatory fields depending on the selected template. Now, the same field can be used in different templates, ask them different postural signature, and in fact it would be nice and labeled in different templates which of these fields are required! -
Is the password field compatible with the "required" option? I only ask because if I make it a required option when editing a page if I haven't changed the password, it throws a required error. Obviously I'd like for the user to be able to leave it blank and leave the password how it is. The problem is if I don't make it required then I may end up without a password at all. Is this something I should look to triggering via a module? Thanks.
-
Does anyone know if it's possible to configure the images field to require description text? A fallback would be to write an onsubmit handler in javascript for the admin - but if it's possible to enforce at the configuration level, that seems like a much cleaner solution. EDIT: the core image field is already in heavy use. If possible, I'd like to modify existing instances rather than create a custom field.
