Scanning Barcode returns Ticket with ID 0 has been checked in

[Maurice]

When scanning the ticket barcode whilst logged in as admin, I get the message Ticket with ID 0 has been checked in, and the ACTUAL ticket doesn’t get checked in.

Using SCAN and QRAFTER – on an iPhone same result with both

The actual ticket has a prefix of WT1 and the number 1, so ticket ID should be WT1-1

Will be a great time saving feature if I can get it to work

[Brian]

Hi,

Thanks for using our plugins. I can help out here.

There is a bug with the new human readable ids causing this. I have created a patched version to help this:

Please follow these steps to change the plugin:

Manual Updates

You will have to resend the ticket emails, which you can do from the WooCommerce Order Actions for the QR link to be correct.

This fix will be included in 4.2.1, which we hope to release in a week or so.

Let me know how that works out.

Thanks

[Maurice]

Hi Brian,

Almost but not quite. The ticket ID I scanned was 12909 but the item reported as checked in when I did the scan was 12910. However When I checked the attendees, the correct ticket 12909 was marked as checked in. So we’re one number out. Not an ultra major problem but a bit confusing if you are also trying to tick off on a printed list.

[Brian]

Hi,

I think there is some confusion on the Order Number and the Ticket Number they will not match as they are post ids.

So it is checking in the right ticket from my tests it just does not show the human readable number so it makes it look like it is off.

That will be fixed in 4.2.1.

Cheers

[Maurice]

Yes I noticed it wasn’t the actual Ticket number which would be the ideal. And since this is going to be fixed in the next release I’m happy to wait. I was aware however that was the post ID’s that were being reported.

Ticket with Post ID 12909 sent via email, When scanned – Post ID 12910 reported as being checked in (this on the iPhone using scanner software). When checking the attendees list, 12909 correctly showing as checked in

Post ID 12910 had actually deleted from the system prior to this test commencing. (moved to Bin) Maybe this has something to do with the issue?

For safety however, I’m going to remove all ticket sales, create a new ticket with a different numbering scheme and retest. I’ll post results tomorrow.

• This reply was modified 9 years, 10 months ago by Maurice.

[Brian]

Ok I was still not able to reproduce this issue, but let me know what you find out.

Thanks

[Geoff]

Hey there,

Just want to drop a quick note in here to let you know that Event Tickets Plus 4.2.1 is about to release any moment and it will include a patch for this issue. Please update and let us know if you continue to hit any trouble.

Thanks so much for your patience while we worked on this!

Cheers,
Geoff

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts