Support

July 25, 2016 at 12:37 pm

Hi M,

Here’s what changed in the 1.0.9 version of the ticket scanning add-on:

Added: Some context to the response for being able to determine server side whether check-in action was triggered via a button click or not (or just via continuous scanning).

Added: A filter around the check_approved condition for validating registrations during check-in actions so that one can change default behaviour. This filter receives the response object setup in the module so that user’s can specify behaviour dependant on context in the callback they register.