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
I am currently translating event espresso’s front end with a localisation plugin. The problem I now have is that now, when I try to register for an event, I get this answer : An error occured. The primary attendee could not be found.
Here is my website’s registration page http://www.defientreprises.com/inscriptions-defientreprises/
Thanks for your help.
There is a conflict with the current version of Jetpack (version 2.0.4). The previous version (2.0.2) of Jetpack will not break the registration process.
You can revert back to version 2.0.2 of Jetpack by downloading it from here:
Before installing, you’ll need to deactivate and delete version 2.0.4 of Jetpack.
Alternatively, if you’d prefer to stay on versioin 2.0.4 and if you’re comfortable with editing PHP files, you can change one line of code in class.jetpack-post-images.php in the Jetpack plugin. Line 254 will read:
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.