Five Star Restaurant Reservations – WordPress Booking Plugin
Changelog
2.7.14 (2026-04-02)
Updated styling for the view bookings form/table.
The view bookings form now displays a message when there are no bookings on the selected date instead of showing an empty table.
2.7.13 (2026-02-19)
Fixed an issue with translations for certain localized strings in the admin not being applied.
2.7.12 (2026-02-06)
Fixes an issue with the max party size causing the party size dropdown in the booking form to populate with an incorrect maximum in certain instances.
2.7.11 (2026-02-04)
Added the ability to disable/enable individual tables.
Fix for party size field not populating correctly when max party option was set to any size.
2.7.10 (2026-02-02)
Added a time limit/window to reminder, late-arrival and post-reservation notifications (3 hours for reminder and post-reservation, 1 hour for late-arrival), to make sure notifications aren’t sent when they shouldn’t be. If notifications aren’t sent within that time frame, then they will be skipped for a particular booking.
Looking up and cancelling a booking now require an assigned unique booking code by default, in addition to the email address.
2.7.9 (2026-01-09)
Patch for low priority/no impact CSRF vulnerability reported by Patchstack.
2.7.8 (2025-12-18)
Fix: When updating a booking from the admin, notifications were being sent all the time instead of only when the “Send notifications” box was checked.
Modified: Added more status change triggers for sending notifications after updating a booking via the admin (so, now, notifications can also be sent if moving a booking from confirmed to closed, from closed to confirmed and from cancelled to confirmed).
2.7.7 (2025-12-02)
Tested with WordPress 6.9.
Fixed an issue related to reported Wordfence vulnerability.
2.7.6 (2025-11-17)
Added a new “Admin Ignore Schedule” option, so admins can create bookings outside their created scheduling rules and exceptions.
2.7.5 (2025-10-20)
Fixed an issue causing an error to sometimes display when clicking the “proceed to deposit” button in the booking form when using the Stripe gateway.
2.7.4 (2025-10-16)
Update to increase security related to payments and displaying payment summary information.
2.7.3 (2025-09-23)
Updated admin notice capability.
2.7.2 (2025-08-27)
Fixed an issue with location-specific maximums being incorrectly calculated.
2.7.1 (2025-08-19)
Minor bugfix for multiple locations settings
2.7.0 (2025-07-30)
IMPORTANT NOTE: Significant updates have been made to the styling of the “Minimal” booking form layout option. If you are using this layout, we highly recommend that you install the update on a staging environment first and test with with the updated style, especially if you have customized the layout and/or CSS.
Refresh of the “Minimal” booking form layout.
Redesign of the plugin admin.
Added: You can now specify a from alphanumeric sender ID for SMS notifications, to be used instead of the phone number.
Added: You can now search for a booking by phone number on the Bookings admin screen.
Added: A character count warning when creating/editing SMS notifications, to help you prevent sending multiple messages for each notification.
Changed: Daily summary email now only sends if there are bookings on that day.
Changed: Added a blank entry at the top of the table select dropdown in the edit booking modal in the admin (to allow admins to make a booking that is not assigned to any table).
Changed: Dining Block Length setting can now be changed on a per-location basis.
Fixed: After selecting the required checkbox in the custom field edit screen, and saving your changes, the required checkbox remained unselected within the custom field edit screen.
Fixed: In the ultimate version, if, on the Advanced settings screen, you used the “Global” dropdown to select a scheduling rule, then opened it again and selected All, it wouldn’t populate any options.
Fixed: In the front-end booking form, if using the blank party size option, if you selected a date and time while the party dropdown was still blank, it would show a false alert saying no table is available, until you selected a party size.
