How to make check-in impossible without cancelling or deleting registrant

Hello,

I have a past event with several noshows. It is still possible to use a ticket on subsequent events; the check-in function still works. But I want to invalidate the ticket so use is not possible anymore.
We need to keep the registrant record & I do not want to inform the registrant by mail of cancelling. There is a button "unpublish", but that seems to do nothing.
Version 3.17.4 installed.

Any hints are much apreciated,

Regards, Frans
 

Hi Frans

The easiest way would be going to Events Booking -> Registrants, check on checkbox next to these registration records, and press Check-in button in the toolbar to change checked in status of these registration to checked in and they won't be able to checkin anymore

Regards,

Tuan

Hello

I improved the code in the extension to handle this use-case better. Now, when you checkin, if the event is a past event (the system compares current date time with event date an event end date to determine if an event is a past event), check in will be fail with a message such as Check-in failed, the event is a past event. That should address your concern without having to do anything

If that works for you, you can access to My Downloads menu item, download latest package, upgrade it to your site to use this improvement

Regards,

Tuan

Hi Tuan,

This is actually exactly what I was looking for!

Some background about the use case:
- I need to keep a record of no-shows. We have a policy of refunding noshow if a valid reason is given (for example positive coronatest). In that case a check is needed if the ticket is actually used.
- Venues have limited place availability. So we overbook some places. To know how much we can overbook we need to know number of no-shows in the past.

Thank you for your action. I will test it and report back. Will take some days, as being a volunteer my time is limited.

Regards Frans

OK Frans. Please update us with the result once you tested it

Regards,

Tuan

Hi Tuan,

I tested the following cases:
1. check-in before end of the event works normally using all methods. As expected
2. check-in using [TICKET_QRCODE] is allowed before end time of event, and gives check-in failed after that time. This is the desired behaviour.
3. check-in using [QRCODE] is allowed before and after the event. This is not expected. It is expected to fail for past events.
4. check-in manually using back-end registrants list works, regardless of event date. As expected.
5. check-in manually using front-end registrants list also works regardless of event date. I would expect it to fail for past events. However, my use case is that I use the front end only for check-in purposes. There are probably other uses for front-end management of registrants which would require a check-in after end of event. I can live with this behaviour. Manual check-in hardly occurs, only when QRcode is not readable. In which case there are instructions to check the validity of the ticket.

My conclusion is (case 3) that I would like a failed messsage for a past event also when using the [QRCODE] method.

Regards Frans

Hello Frans

1. We actually only handle that for [TICKET_QRCODE] tag only.

2. For checkin from registrants management screen, we will do not check it at the moment. It's up to users who manage registrants to do it (in theory, there is no difference between frontend and backend registrants management, it's handled by users with right permission, so they should know what they do)

Regards,

Tuan

Hello Tuan,

Thanks for information. Its a pity that only [TICKET_QRCODE] is supported and none of the other methods of check-in. I will need to migrate to [QRCODE] and native scanning some time in the future.

Regards, Frans

Hello Frans

The reason is because [QRCODE] just contains an URL to checkin registrants. When it is scanned, it just redirect users to that URL to checkin registrants, something is not fast and efficient

I would suggest you to use [TICKET_QRCODE] tag if it is possible

Tuan

Hi Tuan,
the code enhancement also works for future events. let me explain: a year ago I had a user who accidentally presented me with the qrcode of a ticket for an event that was to be held a few days later. The qrcode scanner was still successful by checking in. Does your code improvement also concern this case I described to you above?