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: December 17, 2012 at 6:51 am

Viewing 3 reply threads


Greg Hard

December 17, 2012 at 6:51 am

Hi,

We’re experiencing a brand new error when someone submits a registration, they get this message:

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

It looks like their registration was successful but they get this error. I tried reuploading template files, no go. Any thoughts? We’re running most recent version of Event Espresso and WP.

http://www.clubsatcrp.com/group-fitness/

Thanks.


Greg Hard

December 17, 2012 at 7:25 am

Fixed by disabling most recent version of Jetpack…


Jed Barish

December 17, 2012 at 12:43 pm

Same here! I had to disable Jetpack but its a disappointment! We need to fix the system to be compatible with Jetpack. Its very useful for us :(


Josh

December 17, 2012 at 4:54 pm

I can recommend using the 2.0.2 version of Jetpack for the time being. This may be a bug in the latest version of JetPack.

You can download JetPack version 2.0.2 from this page on WordPress.org:

http://wordpress.org/extend/plugins/jetpack/developers/

Viewing 3 reply threads

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.

Event Espresso - Staging Server