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
An error occured. The primary attendee could not be found. | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › An error occured. The primary attendee could not be found.

An error occured. The primary attendee could not be found.

Posted: February 3, 2014 at 5:55 am

Viewing 1 reply thread


Claire Townsend

February 3, 2014 at 5:55 am

I have the multi event registration and user management plugins enabled and the customer can choose two or more events to add to their cart. This all works fine, one invoice is generated for example.

However when I use the ‘Edit Registration’ shortcode in an email template, the user can amend the first event ok – but the second event (which is sent on a separate email), brings up the edit page with the correct details, then the ‘Confirm Registration’ page, but when you click confirm, it shows the following error ‘An error occured. The primary attendee could not be found.’.

This error only occurs when the status of the registration is pending or incomplete, once completed they user can update both events successfully, but as my users can pay by Cheque this is crucial.

Anyone experienced this, or know a fix?

Thanks


Josh

February 3, 2014 at 1:20 pm

Hi Claire,

I followed up with your email.
Viewing 1 reply thread

The support post ‘An error occured. The primary attendee could not be found.’ 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 Josh 10 years, 11 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server