Actions & filters
Fast Events has a number of action- and filter hooks that can be used to inject custom specific code. Take a look at the examples paragraph of the functions to get an idea how to use them.
If you want to use the filter and action hooks, there are generally a few options.
You add your code to the
functions.phpfile of your theme. The downside of this approach is that every time your theme gets an update you have to redo your changes.
Add it to a function in a child theme. This way you don’t have to redo your code if the theme gets an update, but it requires more knowledge.
Write you own plugin. You have to be a seasoned developer to go down this path.
Or…. use a plugin that does most of the magic for you. If you just want to use a limited set of filters and or action hooks we strongly advice you to take this route. Install the Code snippets plugin. All the examples in the functions can be easy copied into
Snippetsof this plugin. Most examples are easy to understand and easy to adjust.
If you have made a nice snippet yourself, let us know, and we will include it in the documentation as an example.
This filter is called after a custom order status change from the order contextmenu. It can only be used if the ‘Custom order statuses’ field has been set in the plugin settings.
This action is called after an order email has been send to the email-provider (Host-email, SMTP, Amazon SES, Mailgun, …). This call is made with both a successful email and an incorrect email (submission failed).
This filter is called after a basic check of all input and ticket fields.
This action is called after the payment has been received and the customer has already received an email.
Filter the default error text while processing the order and change the text if necessary.
This filter is called if there is a scan error. Normally the API returns the localized error, but you can override it and create your own version. You can make the error-string even more specific by using the scancode that is linked to a specific entrance.
This filter is called just before the output is sent back to the Android or IOS scan app. You can change any of the text lines in the qrcode block.
This action is called after the ticket has been scanned.
This filter is called just before the text of the qrcode block is printed on the ticket template.