Weave Code
Ti Ext Reservation Laravel Package
tastyigniter/ti-ext-reservation
Comprehensive reservation management for TastyIgniter. Let customers book tables online while admins manage bookings, auto-assign tables by availability, set time intervals, stay time, capacity and lead times, send confirmation emails, and automate notifications for every location.
The TastyIgniter Reservation extension adds a complete table reservation system to your restaurant site. Customers can book tables online while administrators accept, track, and manage bookings from a single dashboard.
It supports auto table assignment based on availability, configurable dining areas and tables per location, and a status workflow shared across locations. Reservation settings let you control time intervals, stay time, guest capacity, lead time, and cancellation windows.
- Auto table assignment for incoming reservations
- Customizable settings: intervals, stay time, capacity, lead time
- Confirmation emails to customers, locations, and admins
- Dining area and table management per location
- Automations for notifications and follow-up actions
Frequently asked questions about Ti Ext Reservation
- How do I install tastyigniter/ti-ext-reservation in a Laravel application?
- Install it with Composer using composer require tastyigniter/ti-ext-reservation inside a TastyIgniter application. It is a TastyIgniter extension rather than a standalone Laravel package, so it should be enabled through the TastyIgniter extension manager or your deployment workflow. After installation, run the required migrations and configure reservation settings in the admin area.
- Does tastyigniter/ti-ext-reservation support Laravel 10 or Laravel 11?
- Laravel version support is driven by the TastyIgniter core version you run, not by the reservation extension in isolation. Check the TastyIgniter release requirements for the matching Laravel version before upgrading. Pin compatible TastyIgniter and extension versions until you have validated the reservation workflows in staging.
- How does location-based filtering work in ti-ext-reservation v4.1.4?
- Version 4.1.4 strengthens location-aware reservation handling by enforcing scoped updates, so operations such as status changes can be tied to a specific location. This reduces unintended cross-location side effects in multi-location restaurant setups. Applications that relied on implicit global updates should audit calls to methods like updateStatus() and syncCalendarEvents() and pass location context explicitly.
- How do I update a reservation status for a specific location in TastyIgniter?
- Pass the relevant location into the reservation status update call, for example by providing the location argument to updateStatus() as supported by your installed version. Avoid calling global update patterns when the business rule is branch-specific. Test the change in staging to confirm that only reservations for the intended location are affected.
- What happens if I call updateStatus() without a location parameter in ti-ext-reservation?
- The main risk is that the update may not apply as expected or may affect a broader scope than intended, depending on your code path and installed version. The v4.1.4 location filtering changes mean existing global update assumptions should be reviewed rather than trusted. Audit calls, add explicit location context where needed, and verify behavior with query logging in a non-production environment.
- How do I configure reservation time intervals, stay time, lead time, and cancellation time?
- These are configurable reservation settings exposed by the TastyIgniter reservation extension. Administrators can define reservation intervals, table stay time, guest capacity, lead time, and cancellation time through the extension settings. Review the official TastyIgniter reservation documentation for the exact admin screens and location-specific behavior.
- Does the reservation extension auto-assign tables and manage dining areas per location?
- Yes, the extension includes auto table assignment based on availability and provides dining area and table management for each location. This supports multi-location restaurants that need separate floor plans and table inventories. You should still validate table assignment rules and capacity settings for each location before going live.
- How can I test reservation confirmation emails and automations in TastyIgniter?
- Use a staging environment with test reservations and configured mail drivers so you can inspect customer, location, and admin confirmation emails. The extension supports reservation status workflows and TastyIgniter automations for notifications and actions. Exercise each status transition and automation trigger to confirm that location-aware reservation updates do not skip expected notifications.
- What are alternatives to tastyigniter/ti-ext-reservation for Laravel table bookings?
- Alternatives depend on whether you need a full restaurant management platform or only a booking component. TastyIgniter with this extension is a good fit when you already use TastyIgniter for restaurant operations. For standalone Laravel applications, evaluate dedicated booking packages or build a custom reservation model with your own table availability and notification logic.
- How do I audit and migrate existing code for location-aware reservation updates?
- Scan for calls to updateStatus(), syncCalendarEvents(), and any custom queries that update reservations without explicit location context. Add location arguments where the operation is branch-specific, and test for silent failures or unintended global updates in staging. Update internal documentation and consider version pinning until all reservation workflows have been migrated.
Weaver
How can I help you explore Laravel packages today?