Also – can we get the booking reminder emails variable to respect hours / time? At the moment, for all day bookings, the email is getting sent out at midnight the day before – why can’t we use hours in the schedule variable? I want the reminders to be sent at 6pm:
Currently only works with this:
{{ booking.start_date | modify: ‘-1 day’ }}
Would be good to be able to do this:
{{ booking.start_date | modify: ‘-36 hours’ }}
Or even better, to be able to specify a time
{{ booking.start_date | modify: ‘-1 day @ 18:00 hours’ }}
Matthew Harris: So if I wanted to send an email out on the last day of the booking, and I used the trigger as "booking status changed" from processing to completed (this is when an order is shipped out) what would my trigger be?
Once installed it will add a booking status option into the rules section, so you can say booking status "is not" cancelled. The rule is evaluated at creation and at trigger, so it will pass at the start, and then fail if the booking is cancelled in the interim.
Also – can we get the booking reminder emails variable to respect hours / time? At the moment, for all day bookings, the email is getting sent out at midnight the day before – why can’t we use hours in the schedule variable? I want the reminders to be sent at 6pm:
Currently only works with this:
{{ booking.start_date | modify: ‘-1 day’ }}
Would be good to be able to do this:
{{ booking.start_date | modify: ‘-36 hours’ }}
Or even better, to be able to specify a time
{{ booking.start_date | modify: ‘-1 day @ 18:00 hours’ }}
Matthew Harris: So if I wanted to send an email out on the last day of the booking, and I used the trigger as "booking status changed" from processing to completed (this is when an order is shipped out) what would my trigger be?
Matthew Harris: Nice!
This is already possible. You set the trigger as "booking status changed" from any to "paid".
Then for timing its ‘schedule with a variable’ and use this to trigger it:
{{ booking.start_date | format: ‘custom’, custom-format: ‘YmdHis’, modify: ‘-7 days’ }}
and then the only issue is that this will trigger even if the order is later cancelled.
You can use this plugin I wrote to solve this https://bitbucket.org/rtpdesign/runthings-aw-rule-wc-booking-status/
Once installed it will add a booking status option into the rules section, so you can say booking status "is not" cancelled. The rule is evaluated at creation and at trigger, so it will pass at the start, and then fail if the booking is cancelled in the interim.