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
Suggested feature: number of tickets purchased per attendee in attendee table | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Suggested feature: number of tickets purchased per attendee in attendee table

Suggested feature: number of tickets purchased per attendee in attendee table

Posted: July 25, 2012 at 5:56 am

Viewing 4 reply threads


sp

July 25, 2012 at 5:56 am

Is this something you guys are considering for a future release?


Josh

July 25, 2012 at 8:33 am

I will need to check with the lead developer on this. Can you elaborate a bit more on what you’re looking to do?


sp

July 25, 2012 at 8:42 am

To elaborate, I am referring to the table of an event’s attendee list. So the table that display’s attendee names, their payment status, etc. Check the attached image as an example, with the column I’d like to see in red:

http://s19.postimage.org/f8o03g381/feature.jpg


Josh

July 25, 2012 at 9:42 am

I had a chat with the lead developer about this isn’t going to be added. The reason is if this were added to the table, it would have to calculate that number on the fly, which would really slow that query down. Especially if there were a lot of attendees.

Below is a link to a screenshot of 3.2’s registration overview. Note that with the first three events each have two people that were registered together. Registrations from the same session will be grouped together: http://www.screencast.com/t/kcRYPVOJCv

They are also grouped together on the transaction details page at the bottom under “Attendees registered in this transaction”: http://www.screencast.com/t/BfogkWkH0cYg

  • This reply was modified 12 years, 7 months ago by Josh. Reason: updated screenshot link


sp

July 25, 2012 at 12:43 pm

Hey that’s just as good… my goal is to be able to cut a section of the table and paste it in an email without having to edit it with quantity of tickets per row. If one person buys two tickets, and their name appears twice, that’s just as useful. Thanks for finding out!
Viewing 4 reply threads

The support post ‘Suggested feature: number of tickets purchased per attendee in attendee table’ 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.

The original Forum description...

Status: closed

Updated by sp 12 years, 7 months ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server