|
Austin Ginder
|
May 5, 2015 at 6:22 pm
We are using the EE4 to sell tickets for our events. We purchased the printable tickets and ticket scanner add-ons to allow us to use barcodes to check-in people as they arrive for the event. We recently held our first event and were scanning people in just fine for the first 15 minutes or so and then one of the users accidentally closed the browser and upon reopening, was unable to find that event in the drop down on the barcode scanning screen. I was able to replicate the issue, but do not know what caused it. We had another datetime for the same event later that evening and the event was still now showing. Future events are showing in the drop down, so I am thinking that perhaps there is setting that prevents past events from showing in the drop down. However, in this case, the event duration extended beyond the time in which we were checking people in. Is there a particular setting we need to manage that controls which and/or when events display in the barcode scanner dropdown?
Thanks in advance!
|
|
Josh
|
May 6, 2015 at 9:06 am
Hi Austin,
It turns out that the dropdown where you select an event + datetime only grabs datetimes that are upcoming or active. If the datetime end is in the past, it does not grab those.
We’ve got an open ticket to add a filter there so you could change it to pull in all expired or recently expired events. In the meantime, you can set the datetime’s end time to a later time so you can continue scanning through the duration of the event.
|
|
Austin Ginder
|
May 11, 2015 at 10:48 pm
Hi Josh, It sounds like the new filter will help, but to clarify, in this case the datetime end date for the event was still on the same day and the end time was later in the day than when the scanning was taking place.
|
|
Dean
|
May 13, 2015 at 1:41 am
Hi Austin,
While I believe that this occurred, I have run some tests and have been unable to recreate the issue.
Can you confirm what version of EE, EE ticketing and EE Barcode you were using at that time?
Also if you could provide details of the events datetimes/tickets (screenshots would be great) and the date & approx. time that this issue happened that would be wonderful. It will allow me to attempt a test that is closer in structure to what you have.
|
