This suggestion has been closed automatically because it did not receive enough votes over an extended period of time. If you wish to see this, please search for an open suggestion and, if you don't find any, post a new one.
This doesn't make sense. You want members to choose a prefix, but a "no prefix" option is available. That is counter to your need and for mine. Having a no prefix defeats the purpose of having members forced to pick.
If "No Prefix" wasn't there, an actual prefix would need to be selected by default. What happens then? People ignore it and submit it as is, just going with whatever the default prefix is instead of actually picking one.
EDIT: Just to check; you do realise that "No Prefix" being selected where a prefix is required, results in an error saying they must select a prefix, right?
If "No Prefix" wasn't there, an actual prefix would need to be selected by default. What happens then? People ignore it and submit it as is, just going with whatever the default prefix is instead of actually picking one.
EDIT: Just to check; you do realise that "No Prefix" being selected where a prefix is required, results in an error saying they must select a prefix, right?
Why does a default need to be selected? Why is a no value not possible and then have the submissions process check and if no value, throw and error and make the user pick.
I understand now that something must be loaded into the drop down initially and that a blank space is not optimal because the user then has no indication of what the drop down is used for. However at some level having "no prefix" listed gives me the feeling that "no prefix" is a valid option.