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
How do multiple ticketing entry stations stay in sync? | Event Espresso - Staging Server

Support

Home Forums Ticketing How do multiple ticketing entry stations stay in sync?

How do multiple ticketing entry stations stay in sync?

Posted: September 16, 2013 at 9:02 am

Viewing 2 reply threads


Rob Mougey

September 16, 2013 at 9:02 am

Hi –

The Ticketing Services page mentions: “Have multiple entry stations that synchronize in real-time.” How close to real-time does that actually work? E.g. if I use use iPad “A” to scan a ticket for John Doe, at what point does someone using iPad “B” see that? Would they have to do a refresh of the attendees screen?

Suppose John Doe had given a copy of his ticket to a friend and iPad “B” scanned that copy without having done a refresh of some sort, it would still flag John Doe as having already been checked in, right?

Thanks!


Seth Shoultes

  • Support Staff

September 16, 2013 at 9:40 am

Whenever a ticket is scanned, the app sends and receives a response from the server to check whether or not the ticket is valid, has been checked previously, etc. As far as the attendee listing are concerned, they will need to be refreshed, but if you click on an attendees name, the app will connect to the server to pull the latest data for the attendee.

I hope that answers your questions?


Rob Mougey

September 17, 2013 at 6:36 pm

Yes, thanks!

Viewing 2 reply threads

The support post ‘How do multiple ticketing entry stations stay in sync?’ 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.

Event Espresso - Staging Server