A custom field of type \"dropdown\" that\'s been marked as a required field never actually ends up being required. The red star appears on the front end indicating it\'s required. But selection of any of the field values lets the form submit. I\'ve tried creating a null field value as the first entry in the dropdown list, but that doesn\'t do it. Bottom line is that users can get by with skipping the dropdowns altogether. Seems a pretty straightforward update to the Javascript validation would resolve this (look for a null value if the field is required). Or, by default, add a null value to every dropdown, and if that\'s still selected when the form gets submitted, throw an alert. Thanks!
Any update as to whether this "bug" can be supported by the development team? I've already tweaked the code on my installation, but it would be nice to have it also integrated as a bugfix on the next release. Thanks!
Dropdown field type marked as required
15 years 1 month ago #5335
mrcctv
Visitor
Anyone found a solution to this problem. I would really like to use the dropdown menus instead of radio buttons as the radio buttons use up a lot of real-estate on the page.
One thought comes to mind it can be simple as the first option flags the error. If someone could point me in the right direction maybe I can take a stab at it.
This thread is very old and this problem is still here. Why are we getting new features when something as simple as this does not work?
When i create a dropdown field, set it to required, and leave selection blank, it simply picks the first value and lets the user go through the end of registration wiht no errors.
PLEASE THIS MUST WORK, IT IS THE MOST BASIC OF FUNCTIONS FOR A FORM.