Changelog - Yeti Delivery Slots Documentation

1.0.2

Fixed: if a late payment's time can't be saved at all (a database error, the lock is busy, or the slot was deleted), the order is no longer treated as having its time. It is flagged "Not saved - action needed" in the orders list and on the order, listed in a notice on the orders and Delivery slots screens, noted on the order, and the shop is emailed. It is tried again every hour, and staff can save it again or choose a new time from the order screen
Fixed: an order is only flagged over capacity once its reservation has actually been saved, and only a full or closed time is kept over capacity
Fixed: changing an order's time is now one database statement on the order's single reservation, and a unique key stops an order ever having two reservations. The upgrade removes any duplicates left by older versions, keeping the one that matches the time saved on the order
Fixed: releasing unpaid times uses the same lock as taking a time, so a payment that arrives during the cleanup waits for it and then takes the time again. Whether an order's time has been released is now read from the reservation itself, so an order can't be left wrongly shown as released

Fixed: a late payment for an order whose time had expired no longer takes the place back without checking. It goes through the same locked capacity check as checkout; if the time has filled up, the paid order keeps its time, is flagged over capacity and the shop is emailed
Fixed: releasing unpaid times can no longer remove a reservation that was paid for or renewed at the same moment - each release re-checks that the reservation is still unpaid and expired
Fixed: changing an order's time saves the new time before removing the old one, so a database error can never leave an order without its booking
Fixed: releasing unpaid times works through every expired hold from a saved position, so holds that keep failing can no longer stop newer ones being released
Fixed: the "time changed" customer email and the over-capacity alert are saved on the order together with the change, then sent; if sending is interrupted or the mail server refuses, they are retried hourly (up to 3 attempts, then an order note)