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 Help: Group attendees by Reg ID | Event Espresso - Staging Server
We are implementing an instance of Event Espresso which allows a user to register multiple attendees to form a “Team”. The primary attendee is asked to provide a “Team name” in the form of a custom question group.
We are looking to be able to group attendees in the WP backend by their “Team name” or, if that is not possible, simply by their Reg ID. This would ideally provide us with a way to view “Teams” individually.
Is this a case of writing our own custom page to group attendees or does Espresso provide a way of doing this without modifying anything?
You may be able to use the Custom Files to create a shortcode to display the different team names (by grouping them by that custom question for the team name). However, I’m not sure if that would work.
Otherwise, the attendee exports do group the attendees and assign them group numbers.
Thanks for your reply. I ended up writing a custom function to display a list of group bookings based around a little query to the effect of:
<code>SELECT *
FROM wpevents_attendee AS at
WHERE at.payment_status = 'Completed'
GROUP BY at.registration_id
HAVING COUNT(*) > 1</code>
Viewing 2 reply threads
The support post ‘Help: Group attendees by Reg ID’ 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.