- How do I install tastyigniter/ti-ext-local in a Laravel TastyIgniter app?
- Install it with Composer using composer require tastyigniter/ti-ext-local, then enable the extension and run the TastyIgniter extension setup or migrations required by your version. Because it is a TastyIgniter extension, follow the official Local extension documentation for admin enablement, permissions, and any publish steps. Verify the package version in composer.json so upgrades are intentional.
- Which Laravel and TastyIgniter versions does ti-ext-local support?
- ti-ext-local is built for TastyIgniter, which runs on Laravel, and the package follows modern PHP and Laravel conventions. The provided context does not list exact Laravel version constraints, so check the package's composer.json on Packagist and match it to your TastyIgniter version. Review release notes for type-safety changes before upgrading.
- How do I configure Google Maps or OpenStreetMap geocoding for nearby location search?
- The extension supports multiple geocoding drivers, including Google Maps and OpenStreetMap, with API keys and service-specific settings managed externally. Configure the driver and credentials in your TastyIgniter settings, then test nearby searches with known addresses. For production, add caching or a fallback driver to reduce rate-limit and outage exposure.
- How do delivery zones and delivery area boundaries work in TastyIgniter Local?
- Delivery areas are modeled through LocationArea and related observer logic, supporting boundaries such as circles and polygons with per-location charges. This abstracts common spatial checks so you do not need to write raw geospatial queries for standard delivery-zone validation. Complex operations such as polygon intersections may still require additional tooling like PostGIS.
- How do I set location-specific opening hours and timeslots?
- Each location can have its own opening hours and schedule-driven availability, including timeslot resolution handled by the extension. Set schedules per location in the admin and verify how future-order settings interact with closing days. The v4.3.1 release specifically corrects an edge case in timeslot window search.
- Why are no timeslots available after upgrading to ti-ext-local v4.3.1?
- v4.3.1 fixes a timeslot window search bug that could return false no-availability results when future orders were disabled and a weekly closing day fell inside the two-day lookback. After upgrading, re-test availability end-to-end for locations with weekly closing days near the search window. Remove any cached or hard-coded no-slots fallbacks built around the old behavior.
- Can customers search for the nearest location by address?
- Yes. The Local extension provides nearby location search so customers can enter an address and find the closest branch based on your configured geocoder and location data. Results depend on accurate location coordinates and a working geocoding driver. Test with representative addresses and consider fallback behavior when geocoding fails.
- How do I enable location reviews and custom location fields?
- The extension includes location reviews so customers can rate individual locations, with Blade templates and APIs available for frontend integration. Custom location settings let you add extra fields to store additional location data. Enable reviews in settings and review the provided templates before customizing the UI.
- How should I test ti-ext-local and handle geocoder outages in production?
- Test in a staging TastyIgniter app with real geocoder credentials, covering nearby search, delivery-zone checks, opening hours, and timeslot availability. Mock or stub external geocoding calls in automated tests where possible, and include failure-path tests for rate limits and outages. In production, monitor API usage, cache geocoding results, and configure a fallback driver such as OpenStreetMap.
- Is ti-ext-local maintained, and what alternatives or upgrade concerns should I know?
- The v4.3.1 release and recent type-safety, index, and eager-loading work show continued maintenance without architectural churn. Before adopting it, review composer constraints for your TastyIgniter and Laravel versions and re-check subclass overrides if you redeclare Location method return types. For alternatives, compare other TastyIgniter location extensions or custom Eloquent and geospatial implementations only if you need features beyond its location, delivery-zone, schedule, and review modules.