If you require a prefix for a forum, the option for no prefix should be hidden
But I don't want a default prefix, yet I want to require users to choose from a selection of prefixes. I have this setup on several of my forums.You can set a default prefix in the node's options.
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.
No, it does the opposite.Having a no prefix defeats the purpose of having members forced to pick.
Why wouldn't it just throw an error as if they hadn't picked one?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.
If that is the case, isn't it easier to just hide it so not to confuse members into thinking they have the option of not using a prefix?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?
To repeat, which default prefix would be selected?If that is the case, isn't it easier to just hide it so not to confuse members into thinking they have the option of not using a prefix?
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.How would you...
- Not have a default prefix
- Not have the "no prefix" field
- Indicate that no prefix was selected ?