Notas da versão 1.25: 1 melhoria 3 correções
Melhoria
- Appointments themselves were never affected. The appointment record, availability and the double-booking checks all read the submitted values directly, so only the entry value and the text in notification emails were wrong. No booking data was lost.
Correção
- The appointment date and time arrived in notification emails, confirmations and the entry list as raw serialized data, for example a:3:{s:4:"date";s:10:"2026-09-30";s:4:"time"; s:11:"15:00-18:00";s:4:"cost";s:1:"0";} instead of the booked date. This affected forms with AJAX enabled on Gravity Forms 2.9 and later. Gravity Forms 2.9 changed AJAX-enabled forms to submit through admin-ajax.php, which WordPress reports as an admin request. The Booking Calendar field skipped its date-to-text…
- Entries already saved with a serialized date now display correctly without being re-saved. The entry detail screen, the entries list and notification merge tags all recover the stored booking and format it. Emails that were already sent cannot be corrected retroactively.
- A multiple-slot booking submitted with no slots selected could store an empty array in the entry, which then appeared as serialized data for the same reason as above. The value is now always converted to text before it is saved.