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
how did we get a blank registration? | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium how did we get a blank registration?

how did we get a blank registration?

Posted: March 3, 2014 at 7:16 pm

Viewing 3 reply threads


mamamojo

March 3, 2014 at 7:16 pm

just set up ee and have launched our first event. i noticed one attendee (that is correctly labeled incomplete) has no information in any field. can a blank form be submitted? is this just an abandoned registration?

after a bit of googling, i did turn the confirmation page off in order to avoid unconfirmed registrations thinking maybe that had happened with the other incompletes.


Dean

  • Support Staff

March 4, 2014 at 12:12 am

Hi,

The forms are validated with JavaScript, so the only ways a blank registration could happen is if a) there is a JavaScript error on your site stopping it from working (I checked the Hangout site and this is not the case) or b) the user does not have JavaScript enabled in their browser, and failed to fill out the form before hitting submit.

The confirmation page being turned off should have no effect in respect to this.


mamamojo

March 4, 2014 at 5:20 pm

thanks.


Dean

  • Support Staff

March 5, 2014 at 12:55 am

You’re welcome. Please let me know if you have any other questions regarding this.

Viewing 3 reply threads

The support post ‘how did we get a blank registration?’ 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