A deleted Ticket can still be checked in?

[Adam]

Hi

I am testing the refund process and have followed your knowledgebase article on that and stock control etc. All that makes sense.

However, in a situation where I have issued a refund and I want to make sure that customer cannot still check in with their QR code, the article says to delete the ticket(s) in question from the event. That seems reasonable, however, it doesn’t seem to work?

To elaborate…

If I have an event called JSE 1, I will have tickets that are ID’d JSE1-1 through whatever, say JSE1-20. A normal QR code check in for say valid ticket JSE1-8 would show as “The ticket with ID JSE1-8 was checked in.” Fine.

However, if I deleted ticket JSE1-2, and then try to check in that ticket’s QR code (from the email that was sent when it was ordered), I get “The ticket with ID 226 was checked in.”!

I was expecting to see something like “Invalid QR code”, or “Cancelled ticket, not checked in”. And of course, because it was deleted, I cannot get to it to undo the seemingly okay check in? Also, No idea where “226” comes from? It’s not the Woo Order ID…

So – is this a bug?

And regardless, perhaps the “invalidating of a ticket process” would be better if there was a “Validity” column, and all tickets show by default as Valid – and instead of deleting the ticket you have the option of maybe marking it’s validity as either Valid or Cancelled (or any other statuses that might make sense), and then not allow the check in option for those cases (that way you can always change it back to Valid perhaps if a mistake was realised or restitution was made).

[Shelby]

Hi Adam,

I’m happy to help out with this issue, thanks for posting!

I’ve checked our logged bugs, and I don’t see this one, so I’m going to do some testing on my local install to see if I can replicate this issue. In the meantime, could you please go through the steps here to test for a conflict and let me know if there seem to be any conflicts, or if you’re getting the same results with the testing configurations?

Let me know if you have any questions about that!

Thanks,

Shelby 🙂

[Adam]

Hi

I don’t have twentysixteen, but do have twentyseventeen. So…

I switched to twentyseventeen and disabled all plugins except:

• Event Tickets
• Event Tickets Plus
• The Events Calendar
• Woocommerce (needed to keep this active so I could see the attendee list for an event so I could delete a ticket)

The issue still occurs under these conditions.

Thanks

[Shelby]

Hi Adam,

One more question:

Do you experience this when deleting $0 tickets too, or only tickets with a dollar value assigned?

Thanks!

Shelby 🙂

[Adam]

Hi Shelby,

I have tried with £25 tickets, free tickets (£0), and also RSVP tickets. All types let you check in AFTER the ticket has been deleted. However, instead of saying a “ticket ID” is checked in, e.g. JSE1-1, it gives a different value (post ID perhaps?).

Also, to clarify: In all cases I did NOT go through a Woo refund process when testing, as I figured Event Tickets Plus does not actually care about that, just whether or not a ticket has been deleted. So maybe you can confirm that too?

On further view (see attached pics):
– In Attendees list under Attendees tab it shows – Deleted Attendees: 4
– In Attendees list under Orders tab it shows – Canceled: £0.00 (0)

So maybe deleted ticket does not by itself equate to a cancellation?

[Barry]

Thanks for your patience so far, Adam.

You are right – there’s a hole in our logic here and the fact that the ticket/attendee record in question no longer exists should be flagged up when an attempt is made to check them in via QR code.

I will log this and we’ll do our best to get a fix in place in an upcoming maintenance release — our apologies for any inconvenience in the meantime.

[Adam]

Ok – glad I’m not going mad!

I look forward to the fix.

And to repeat a thought I made earlier for a possible future enhancement after this fix is done… perhaps the “invalidating a ticket process” would be better if there was a “Validity” column in the attendee list, and all tickets show by default as Valid. And instead of deleting a ticket to cancel it, you have the option of maybe marking it as either Valid or Cancelled (or any other statuses that might make sense), and then not allow the check in option for those cases (that way you can always change it back to Valid perhaps if a mistake was realised or restitution was made)

Thanks again

[Brook]

Howdy Adam,

Thanks for sharing that idea. It seems to me we could extend the Status column here. It already can show statuses such as “refunded” or “cancelled”. These are driven by the status of the associated order, which in your case can be set in Woo. Already you can leverage this to cancel tickets, but perhaps we could allow more granular control on a per ticket basis without needing to modify the original order?

Thanks again.

– Brook

[Adam]

Hi Brook

Yep – you could indeed extend that status. As long as the option to toggle a ticket’s validity on or off is easy to get to in that list of tickets – i.e. adding an “invalidate / validate” or “inactivate / activate” toggle to the options that show up on hover perhaps – or like the Check-in column have one for that which toggles a ticket’s validity status.

Anyway – was just throwing it out there as I know I’d find it useful – I’ll leave it with you guys 🙂

[Barry]

Thank you – we appreciate exactly this kind of feedback.

[Adam]

Hi,

Any news re when this might be fixed please?

Thanks

[Cliff]

Hi, Adam. Sorry for the delay not answering your question here.

This ticket is in Pending Fix status, which means this thread should receive a reply once the applicable fix has been released. I did bring this up again to our development team’s attention but cannot guarantee when it will be fixed.

I apologize for this issue and appreciate your understanding and patience.

[Nico]

Hey,

A new maintenance release has been recently shipped addressing this issue 🙂

More information in the release notes and hotfix notes.

Please update the plugins and let us know if the fix works for you,
Best,
Nico

[Adam]

Cool thanks – I’ll check it in the next day or so and confirm back.

[Adam]

Just to confirm that it now works as expected. This can be closed now.

Thanks for your help.

[Author]

Posts