- Is tattali/calendar-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle with Symfony heritage, not a native Laravel package. Laravel already relies on Symfony components, so Composer installation is straightforward, but bundle registration and service wiring differ from Laravel package discovery. Expect to add manual service bindings or a maintained bridge if you want to consume it in Laravel.
- How do I install tattali/calendar-bundle with Composer?
- Install it through Composer and verify the PHP and Symfony contract constraints in its composer.json before updating your lockfile. In a Symfony app you register the bundle normally, while in Laravel you will likely need manual service provider wiring or an adapter layer. Trial the install in staging first because Symfony bundle conventions do not map automatically to Laravel.
- Does tattali/calendar-bundle work with Laravel out of the box?
- No, Laravel fit is not native unless a wrapper or manual service binding exists. The package provides a Symfony bundle that integrates FullCalendar with Doctrine-backed event management, CRUD operations, AJAX loading, and configurable views. Laravel teams should confirm request handling, middleware behavior, CSRF, and auth do not interfere with calendar endpoints.
- What changed in tattali/calendar-bundle v8.2.1?
- v8.2.1 is a narrow bugfix in which RequestParser now reads parameters from the POST body instead of the query string. This is effectively an API contract correction rather than a feature change. Any client still sending POST parameters through the query string may break after upgrading.
- Will upgrading to v8.2.1 break existing calendar endpoints?
- It can if existing clients send POST parameters via the query string, because RequestParser no longer reads them from that location. Add regression tests for both POST-body and query-string behavior, then deploy to staging before production. A rollback to v8.2.0 is easy but reintroduces the original parsing bug.
- How does tattali/calendar-bundle integrate FullCalendar and Doctrine?
- The bundle integrates FullCalendar into your application and offers Doctrine-backed event management, CRUD operations, AJAX loading, and configurable calendar views. In Laravel, you must evaluate how to adapt the Doctrine persistence layer or bridge it to your application data model. Confirm the calendar data volume and storage approach before committing to the integration.
- Which PHP, Laravel, and Symfony versions does tattali/calendar-bundle support?
- The package is Symfony-oriented, so you must verify its PHP version constraints and Symfony contracts in composer.json rather than assuming Laravel version support. Check the upstream compatibility details and test middleware behavior in your Laravel version. Laravel request handling must preserve the POST body as expected for v8.2.1 to work correctly.
- How should I test tattali/calendar-bundle in a Laravel app before production?
- Inventory every route or endpoint that depends on RequestParser, then add tests for form-urlencoded and JSON POST bodies as well as query-string behavior. Verify that CSRF and auth middleware do not strip or alter the request body. Deploy v8.2.1 to staging, update clients and API documentation to send parameters in the POST body, and run a production canary while monitoring 4xx and 5xx rates.
- What are the alternatives to tattali/calendar-bundle for Laravel event calendars?
- Laravel teams may prefer a native Laravel calendar package or building FullCalendar directly with Eloquent-backed event storage. The Symfony bundle makes sense if you already depend on its request parsing, Doctrine event management, and AJAX loading conventions. If no maintained Laravel bridge exists, compare the cost of an adapter layer against adopting a Laravel-native alternative.
- Is tattali/calendar-bundle actively maintained and safe for production?
- It is a community-supported upstream package with no commercial SLA implied, so internal ownership is important. Patch-level maintenance is low, but you should track upstream releases and keep an owner for the Laravel or Symfony adapter layer. Document the POST-body contract, maintain endpoint regression tests, and keep a rollback plan for production.