Cannot Select State

The State dropdown field in the subscriber registration form is not offering any values to choose. I have tried mapping to FIELD_STATE to JomSoclal, I have tried adding all 50 states in default value, I have tried adding "state" as field type, but still nothing shows.

Additionally, the form is still being submitted even though it is a Required field. If nothing is available for selection how can it be processed?

Please help - I believe this may be causing issues with allowing people to subscribe.

Here is subscription page

Did you find a fix for this? I just started having the same problem

@Ari: There must be some javascript conflict causing the issue. Please submit a support ticket so that we can help solving it for you

Tuan

We seem to be having the same problem; is there a solution to this issue?

Edit: Logged on with Registered User: No State field when filling out subscription Plan information.

Logged on with active member User: State field appeared

Logged on with Superuser: State field appeared.

So, a permissions issue?

2nd Edit:
Yes, had access permission for State field set to 'Member' rather than 'Registered'. FIXED (for me).

Hmm. Why don't you set access to "Public" so that everyone can see that field ?

Tuan

Good idea. Thanks. Forgot that MP registered Public subscribers. Don't need to restrict access to the fields' information since we don't display it on the front end except to Join.

Ari wrote: Did you find a fix for this? I just started having the same problem

Well I don't know what is going on here, I have the same problem, although I have been using Membership PRO, on several website making sure that my clients get all the time a clean paid download. I am posting this on April 20th 2015. When I try to fill out the form for one of my plan, a message popup and display the word "error", when I dismiss this message I noticed that the state was not showing and that the form was not processing. I hope again that somebody is looking into that issue. Thank you !

Set the field as public.

That mostly causes by javascript conflict. I received support ticket from @2squaredesign, will check and get it sorted within today

Tuan

We are having this same issue as well. I will submit a ticket for it, too.