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 Send attendee_id to user meta issue | Event Espresso - Staging Server
I’m running into a strange situation when trying to grab attendee data.
I can run the ‘action_hook_espresso_save_attendee_data’ hook and use $attendee_data to grab all of the unique data of attendees, even when multiple people are added.
But, $attendee_data[ ‘attendee_id’ ] prints the same for every user.
Thank you for your reply.
In the ‘events_attendee’ table, each attendee has a unique and correctly numbered ID. So, each attendee does have a unique number. It seems that in the Meta Data stored it keeps the number of the primary register. But, in the attendee table they get their unique key. When does that happen and is there a function I can use to grab that unique number at registration?
It seems we are both correct: with standard registration they share the ID, with MER they do not http://d.pr/i/MDm3
I’m not sure of the exact code, but it would happen at the confirmation display point as that is when they are added to the database.
Looking at it, and bearing in mind I am not a developer, it looks to me like MER is being actioned by the event_espresso_add_attendees_to_db_multi function in event-espresso/includes/functions/add_attendees_to_db.php (this is called from the cart.php file), so I would suggest checking that out.
Viewing 3 reply threads
The support post ‘Send attendee_id to user meta issue’ 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.