- What is el-schneider/statamic-calendar used for?
- It is a Statamic addon for Laravel applications that need event and calendar content. It helps you create and manage events, including recurring events, and query that content for calendar listing and detail pages. In v0.8.0 and later, your application owns the routes and templates, so the package is best treated as a content and query layer rather than a complete calendar frontend.
- How do I install statamic-calendar in a Laravel app?
- Install it with Composer as a Statamic addon in your Laravel application, then publish the package assets and examples you need. For v0.8.0, publish the reference implementation with php artisan vendor:publish --tag=statamic-calendar-examples and wire your own routes and Antlers templates. Review the package requirements and Statamic setup before installing in production.
- Does statamic-calendar support recurring events?
- Yes. The addon is described as making calendars with recurring events simple, so it is intended for event content that repeats on a schedule. Recurring event data is managed in Statamic, while rendering and routing are handled by templates and routes in your application after v0.8.0. Test your recurrence cases against your own listing and detail views.
- Why is the /calendar route missing after upgrading statamic-calendar?
- Version 0.8.0 removes the addon-owned /calendar route, so the route must now be registered by your application. Add an app-owned route such as Route::statamic('calendar', 'events/index') or a custom controller route that matches your site structure. If you still get a 404, check that the new route is registered and that its template exists.
- Where are the statamic-calendar index and show templates in v0.8.0?
- The built-in statamic-calendar/index and statamic-calendar/show templates are no longer shipped by the addon in v0.8.0. Use the statamic-calendar-examples package as a starting point and create application-owned templates for your calendar listing and event detail pages. If you already published statamic-calendar-views templates, those published files remain compatible.
- How do I publish the statamic-calendar examples?
- Run php artisan vendor:publish --tag=statamic-calendar-examples to publish the reference routes and templates into your application. Use the published files as a guide, then adapt the routes and Antlers templates to your site's URL and layout requirements. Keep the examples under application source control so your calendar presentation is explicit and maintainable.
- Which Laravel and Statamic versions does statamic-calendar support?
- The exact supported Laravel and Statamic version constraints are defined by the package's Composer requirements, so check its composer.json or Packagist metadata before upgrading. Confirm that your application's Laravel and Statamic versions satisfy those constraints, especially when moving to v0.8.0. If you are on an older Statamic release, test the upgrade in staging before changing production.
- Why does statamic-calendar throw InvalidArgumentException for tags?
- In v0.8.0, invalid tags values now throw InvalidArgumentException instead of silently disabling the filter. This means your tags data must contain valid slugs or valid terms before it is passed to the calendar query. Audit event content and query parameters, fix or remove invalid values, and add tests for single-term and multi-term filtering.
- Is statamic-calendar a turnkey calendar frontend?
- Not after v0.8.0. The addon now expects your Statamic application to own routing and presentation, so it functions more like a content and query package for events. You can use statamic-calendar-examples for a reference implementation, but you should expect to maintain your own routes, templates, and styling. This is a healthier Statamic-aligned architecture but requires more app-level integration.
- How should I migrate an existing site to statamic-calendar v0.8.0?
- Start in staging by auditing routes, collections, and templates that reference /calendar, statamic-calendar/index, or statamic-calendar/show. Publish the examples, create app-owned routes and templates, and keep any previously published statamic-calendar-views templates that are already in use. Remove the obsolete routes key from config/statamic-calendar.php, validate tags content, and run regression tests for listing pages, detail pages, and term filters before deploying.