Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Required Question Not Acting Like Required Question | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Required Question Not Acting Like Required Question

Required Question Not Acting Like Required Question

Posted: July 30, 2013 at 11:31 am

Viewing 2 reply threads


Melissa Plotsky

July 30, 2013 at 11:31 am

Hi guys —

We just added a Phone number field to the Personal Information Question Group. It was marked “required” when we set it up — and the question page shows that it is, indeed, required. However, on the registration page, it’s missing the required asterisk — and users are allowed to bypass it.

All the other questions that we’ve marked required work fine. For some reason, though, this one isn’t. Any ideas?

You can see our reg page here: http://surfballard.com/event-registration/?regevent_action=register&event_id=10

Thanks!

~Melissa


Jonathan Wilson

  • Support Staff

July 30, 2013 at 2:20 pm

Hi Melissa,

I just tested this and am not seeing the problem. I am using the default Phone question and marking it as required. Is that the one you are using?


Josh

July 30, 2013 at 5:03 pm

You might try setting it to not be required, then saving, then set it to be required again and re-save. I’ve found that to help when options don’t seem to save correctly.

Viewing 2 reply threads

The support post ‘Required Question Not Acting Like Required Question’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server