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
attendee scan date information - custom development? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › attendee scan date information – custom development?

attendee scan date information – custom development?

Posted: May 28, 2013 at 1:25 pm

Viewing 1 reply thread


Ben

May 28, 2013 at 1:25 pm

Hi,

I’ve got a client with a ‘General Admission’ event which starts at the beginning of the summer season and ends at the end of the season. Having a recurring daily event is not an option.

What information we would like to be able to retrieve is when the ticket was scanned? example here – http://screencast.com/t/gULDDlfN4

Is this possible to achieve? Would this be custom development?

Thanks
Ben


Seth Shoultes

  • Support Staff

    •

May 28, 2013 at 2:24 pm

Ya, I think we might be able add. It may take some work on the API and the event admin to get running.

You can request more information using this form:
http://staging.eventespresso.com/rich-features/sponsor-new-features/#form
Viewing 1 reply thread

The support post ‘attendee scan date information – custom development?’ 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 Seth Shoultes 11 years, 8 months ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server