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 The primary attendee details could not be retrieved from the database. | Event Espresso - Staging Server
Have only updated the event expresso plug-in to the latest version. 3.1.30.7P
I have tried de-activating and re-activating as I point out in first post. No luck there.
All Event Expresso plugins are current. I have one on the site that is not. However it is not activate at the moment, and has been like that.
One other odd note about this particular record. It is for multiple registrations ($150 each ticket. Also when we look at the amount owed section the Payment Page it is 0 even though no payment has been posted. It should read $750 for the whole order. It is an invoice only.
It sounds like either the primary attendee has been deleted from the db, or that the primary attendee flag has not been set on any of the 5 attendees. Can you confirm that all 5 attendees are present in the attendee list?
All attendees were. However, it appears their were two different orders. The first must have failed. We had attendees in there twice. I have removed the duplicate entries. Sorry I did not notice that sooner.
Viewing 4 reply threads
The support post ‘The primary attendee details could not be retrieved from the database.’ 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.