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
Ticket Scanning | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Ticket Scanning

Ticket Scanning

Posted: February 11, 2013 at 2:39 am

Viewing 5 reply threads


bins

February 11, 2013 at 2:39 am

I ran my first event yesterday, where I was going to trial QR code/ticket scanning.

Unfortunately, whilst the reader (iPhone 4 over 3g) did beep, there was no update as to the validity of the ticket.

I ran trials when I installed the software a couple months ago, but stupidly did did not repeat in recent days.

Has there been an update of the server side software or is it a different issue?


Dean

  • Support Staff

February 11, 2013 at 4:25 am

Hi,

Did this happen on every ticket? Did the website update with check-in confirmation?

There was an update in October 2012 for the Ticket Services files.


bins

February 12, 2013 at 9:04 am

Dean,

when the ticket is scanned, attendance is updated, however, the scanner (phone) locks on the image, with no further verification. I have to either click search then scan to return or go back to the event.

I installed on to my server on 25/10.

Paul


Josh

February 12, 2013 at 5:07 pm

Hi Paul,

It would not hurt to double check and make sure you have the latest version of the ticketing add-on and mobile app api installed. Please see the ticketing documentation for a download link for the mobile app api:

http://staging.eventespresso.com/wiki/espresso-ticketing/

One other thing that would be good to check is whether you have any caching plugins active that are caching the database. While these will not serve a cached version of the database to the WordPress admin, they will serve a cached version of the database to the ticketing app, which will result in the ticketing app not working as expected.


bins

February 13, 2013 at 3:09 am

Josh,

I reloaded the api and all seems well. I probably downloaded and tested it, originally, just before you updated it!

Where do you normally announce when you update these scripts, so I can keep an eye out?


Josh

February 13, 2013 at 8:35 am

The changelog:

http://staging.eventespresso.com/wiki/change-log/#ticketing-api-2.2

Viewing 5 reply threads

The support post ‘Ticket Scanning’ 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