Hi guys,<\/p>\n
I am again facing an issue which I have raised a couple of times before – the previous two support threads can be found with the same title as this one.<\/p>\n
Here is what happens in a test environment:<\/p>\n
1. I create a new event.
\n2. I create one type of ticket for this event. For this test, this is an RSVP ticket.
\n3. Three of my colleagues each RSVP to the event 4 times. Each are issues 4 tickets.
\n4. I begin scanning these tickets using a QR reader for my iPhone to simulate multiple ticket-holders.
\n5. The first few scan OK and are checked in. This is reflected on the back-end.
\n6. After this, about half of the tickets check in normally. The other half give the message “The ticket with ID XXXXXX has already been checked in.” even though they have not.
\n7. The back-end reflects that the scanned tickets actually have been checked in, however the message displayed is incorrect and this will no doubt cause serious confusion at a ticketed event.<\/p>\n
The first time I raised this last year, I was told by Andr\u00e1s that this issue had been recreated and was scheduled to be addressed in a later release.
\nThe second time I raised this in February I was told by Zach that it hadn’t been addressed, but was due to be. I never updated the ticket from here (my fault!) but presumed that this would have been resolved when I updated the plugin.<\/p>\n
Unfortunately we are still having this problem, which is the only issue we’re experiencing with an otherwise excellent product. Any help on this would be greatly appreciated<\/p>\n","protected":false},"template":"","class_list":["post-1359848","topic","type-topic","status-closed","hentry"],"yoast_head":"\n