Space Between Options in Drop-Down Menu

I made a drop-down menu with a large number of choices (about 2,700) for users to choose from. S2Member is automatically inserting spaces in between the choices, blank choices that can also be clicked on. What’s worse is that the actual choices are not being accepted as possible choices, so it is telling the user that they need to pick one of the empty spaces.

To see what this looks like, please visit: http://jailhandbooks.com/for-jail-officials/if-youve-received-a-freedom-of-information-act-foia-request/

If you select the second custom field, “Please select the jail…” you’ll see that spaces are inserted in between the actual choices which I want. This did not happen with the first custom field, the states field, and I do not know why it is happening, since I did not put any spaces in when I inserted the possible options.

Please let me know how to resolve this ASAP. It is very important that this be resolved quickly.

Thank you for reporting this important issue.

It looks like an error with your syntax. s2Member is creating options twice for each of your selections. Could you copy a section of your custom field’s options field so we can take a look, please?

Abbeville County Detention Center |Abbeville County Detention Center
Aberdeen Police Department |Aberdeen Police Department
Acadia Parish Jail Complex |Acadia Parish Jail Complex
Accomack County Jail |Accomack County Jail

The problem could be that I’m listing them twice each… but I really want the “value” to be the same as the display option that the user sees.

It seems that listing the jail names twice was the problem. I’ll just use numbers instead. Thanks!

I made the change to numbers, as in:

2 |Abbeville County Detention Center
3 |Aberdeen Police Department
4 |Acadia Parish Jail Complex
5 |Accomack County Jail

and this has NOT resolved the issue. PLEASE ADVISE. This is quite urgent.

I think the issue is the space between the number and the line. I will try that.

That appears to have resolved the issue.

That appears to have resolved the issue.

Cool thanks for the update. Let us know if problems persist.