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
Registration accepted after registration closed | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Registration accepted after registration closed

Registration accepted after registration closed

Posted: February 3, 2013 at 6:41 pm

Viewing 1 reply thread


Jonathan Brooks

February 3, 2013 at 6:41 pm

Weird one… The event was closed 2/1 at 8am. A user who previously purchased 6 tickets somehow managed to register again for four tickets on 2/3, two days after registration was closed. The price per ticket on her registration shows as $0.00 per ticket and all data fields in the EventEspresso WordPress admin aside from Reg ID (like Event Time, Option, etc.) are all blank. What concerns me is that she received a confirmation email for the 4 tickets… Thanks for your help.


Seth Shoultes

  • Support Staff

    •

February 3, 2013 at 10:00 pm

That is really weird. Do you have a link to the event?
Viewing 1 reply thread

The support post ‘Registration accepted after registration closed’ 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.

The original Forum description...

Status: closed

Updated by Seth Shoultes 11 years, 11 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server