Skip to content
Capell CMS

Events

Package docs status

Section titled “Package docs status”

This page is generated from package source documentation in the Capell packages repository and the checked-in manifest. Source documentation is not distribution status. Before running a Composer command, verify that the exact package and compatible 1.x release are available through public Packagist or the authenticated marketplace account.

Field Value
Composer package capell-app/events
Package slug events
Product group Capell Engagement & CRM
Tier premium
Bundle engagement-crm
Runtime contexts admin, frontend, console
Capell version ^1.0
Catalogue role extension
Release channel Labs
Source repository capell-app/packages
Source path packages/events
Docs source packages/events/docs
Manifest capell.json

What This Plugin Adds

Section titled “What This Plugin Adds”

Events is an Available, Schema-owning Capell plugin in the Capell Engagement & CRM product group. It ships as capell-app/events and extends these surfaces: admin, frontend, console.

Events adds publishable recurring events, generated occurrences, venues, registrations, waitlists, notification scheduling, public calendars, and calendar feeds.

Editors manage events, venues, occurrences, and registrations from resources and an admin calendar. Visitors browse public listings and calendars, subscribe to an ICS feed, and register for available occurrences.

Evidence: capell.json, src/Models/Event.php, src/Actions/SyncEventOccurrencesAction.php, src/Providers/EventsServiceProvider.php, docs/overview.admin.md, docs/screenshots.json, src/Filament/Pages/EventCalendarPage.php, tests/Feature/PublicEventRegistrationTest.php.

Status details:

  • Status: Available
  • Tier: premium
  • Bundle: engagement-crm
  • Composer package: capell-app/events
  • Namespace: Capell\Events
  • Theme key: not applicable

Why It Matters

Section titled “Why It Matters”

For developers: Actions isolate recurrence expansion, occurrence synchronization, registration capacity, waitlist reconciliation, feeds, and structured event data from controllers and UI classes.

For teams: Teams define a recurring programme once, review its dated occurrences, and manage attendance and waitlist changes without recreating each event date.

Evidence: src/Actions/ExpandEventRecurrenceAction.php, src/Actions/RegisterForEventOccurrenceAction.php, src/Actions/BuildCalendarFeedAction.php, tests/Integration/Actions/RegisterForEventOccurrenceActionTest.php, docs/admin-guide.md, tests/Integration/Actions/SyncEventOccurrencesActionTest.php, tests/Integration/Actions/ReconcileEventWaitlistsActionTest.php, tests/Integration/EventRegistrationResourceWorkflowTest.php.

Screens And Workflow

Section titled “Screens And Workflow”

Screenshot contract: docs/screenshots.json.

Events index

Create event form

  • Events index (admin, required).
  • Create event form (admin, required).
  • Edit event form (admin, required).
  • Event venues management (admin, required).
  • Event occurrences management (admin, required).
  • Event registrations management (admin, required).
  • Admin event calendar page (admin, required).
  • Event calendar widget (admin, required).
  • Frontend events listing page (frontend, required).
  • Frontend events calendar page (frontend, required).
  • iCalendar feed route (frontend, required).

Technical Shape

Section titled “Technical Shape”
  • Service providers: Capell\Events\Providers\EventsServiceProvider.
  • Config files: packages/events/config/capell-events.php.
  • Migrations: packages/events/database/migrations/2026_05_10_190848_01_create_event_venues_table.php, packages/events/database/migrations/2026_05_10_190848_02_create_events_table.php, packages/events/database/migrations/2026_05_10_190848_03_create_event_occurrences_table.php, packages/events/database/migrations/2026_05_10_190848_04_create_event_registrations_table.php, packages/events/database/migrations/2026_05_10_190848_05_create_event_notification_logs_table.php, packages/events/database/migrations/2026_05_31_070000_06_add_unique_event_notification_logs_identity_index.php, packages/events/database/migrations/2026_06_07_000000_07_add_notification_keys_to_event_notification_logs_table.php.
  • Models: Event, EventNotificationLog, EventOccurrence, EventRegistration, EventVenue.
  • Filament classes: EventCalendarPage, EventResource, CreateEvent, EditEvent, ListEvents, EventForm, EventsTable, EventOccurrenceResource, ManageEventOccurrences, EventRegistrationResource, ManageEventRegistrations, EventVenueResource, and 2 more.
  • Livewire components: EventCalendar, EventsCalendarPage, EventsListingPage.
  • Route files: packages/events/routes/web.php.
  • Policies: AbstractEventResourcePolicy, EventOccurrencePolicy, EventPolicy, EventRegistrationPolicy, EventVenuePolicy.
  • Extension contracts: EventBookingProvider, EventRegistrationProvider.
  • Events: EventRegistrationCancelled, EventRegistrationCreated.
  • Listeners: PromoteWaitlistAfterRegistrationCancelled.
  • Actions: BuildCalendarFeedAction, BuildEventOccurrenceUrlAction, BuildEventOccurrenceViewDataAction, BuildEventSchemaAction, BuildPublicEventRegistrationUrlAction, CancelOccurrenceAction, EnsureEventPublishingDefaultsAction, EnsureEventPublishingSurfaceAction, ExpandEventRecurrenceAction, InstallEventsPackageAction, InstallPackageAction, ProcessDueEventNotificationLogsAction, and 11 more.
  • Data objects: EventOccurrenceData, EventOccurrenceViewData, EventRegistrationData.
  • Command signatures: capell:events-doctor, capell:events-install.
  • Manifest action API: install: Capell\Events\Actions\InstallEventsPackageAction.
  • Scheduled commands: Capell\Events\Manifest\EventsScheduleContribution (everyFifteenMinutes), Capell\Events\Manifest\EventsScheduleContribution (everyMinute).
  • Console command classes: EventsDoctorCommand, InstallCommand.
  • Manifest contributions: admin-page: Capell\Events\Manifest\EventsAdminPageContribution, admin-resource: Capell\Events\Manifest\EventsAdminResourcesContribution, console-command: Capell\Events\Manifest\EventsConsoleCommandsContribution, dashboard-widget: Capell\Events\Manifest\EventsDashboardFilamentWidgetsContribution, frontend-component: Capell\Events\Manifest\EventsFrontendComponentsContribution, health-check: Capell\Events\Health\EventsHealthCheck, migration: Capell\Events\Manifest\EventsMigrationsContribution, model: Capell\Events\Manifest\EventsModelsContribution, page-type: Capell\Events\Manifest\EventsPageTypesContribution, page-variation: Capell\Events\Manifest\EventsPageTypesContribution, render-hook: Capell\Events\Manifest\EventsRenderHookContribution, route: Capell\Events\Manifest\EventsRoutesContribution, scheduled-job: Capell\Events\Manifest\EventsScheduleContribution.
  • Health checks: Capell\Events\Health\EventsHealthCheck.
  • Blade views: packages/events/resources/views/filament/widgets/event-calendar.blade.php, packages/events/resources/views/livewire/event-calendar.blade.php, packages/events/resources/views/livewire/page/events-calendar.blade.php, packages/events/resources/views/livewire/page/events-listing.blade.php, packages/events/resources/views/registration.blade.php.
  • Cache tags: events.

Data Model

Section titled “Data Model”
  • Required tables: event_venues, events, event_occurrences, event_registrations, event_notification_logs.
  • Models: Event, EventNotificationLog, EventOccurrence, EventRegistration, EventVenue.
  • Core record references in migrations: sites via site_id, layouts via layout_id.
  • Migration files: 2026_05_10_190848_01_create_event_venues_table.php, 2026_05_10_190848_02_create_events_table.php, 2026_05_10_190848_03_create_event_occurrences_table.php, 2026_05_10_190848_04_create_event_registrations_table.php, 2026_05_10_190848_05_create_event_notification_logs_table.php, 2026_05_31_070000_06_add_unique_event_notification_logs_identity_index.php, 2026_06_07_000000_07_add_notification_keys_to_event_notification_logs_table.php.
  • Migration impact: run host migrations through the package install flow before opening package surfaces.
  • Deletion/retention behaviour: migrations declare cascade-on-delete relationships and null-on-delete relationships; no timed pruning or retention schedule is declared in capell.json.

Install Impact

Section titled “Install Impact”
  • Required packages: capell-app/admin, capell-app/frontend, capell-app/navigation, capell-app/publishing-studio.
  • Admin navigation: declares admin-page: EventsAdminPageContribution, admin-resource: EventsAdminResourcesContribution; each Filament page or resource controls its own navigation visibility.
  • Admin/editor extensions: dashboard-widget: EventsDashboardFilamentWidgetsContribution.
  • Permissions: ViewAny:Event, View:Event, Create:Event, Update:Event, Delete:Event, DeleteAny:Event, Restore:Event, RestoreAny:Event, ForceDelete:Event, ForceDeleteAny:Event, Replicate:Event, Reorder:Event, ViewAny:EventVenue, View:EventVenue, Create:EventVenue, Update:EventVenue, and 32 more.
  • Public routes: loads routes/web.php; registers EventsRoutesContribution.
  • Database changes: package migrations are declared.
  • Config: config/capell-events.php.
  • Settings: no package settings declared.
  • Queues or schedules: scheduled commands Capell\Events\Manifest\EventsScheduleContribution (everyFifteenMinutes), Capell\Events\Manifest\EventsScheduleContribution (everyMinute).
  • Cache tags: events.
  • Commands: capell:events-doctor, capell:events-install.

Common Pitfalls

Section titled “Common Pitfalls”
  • Keep required Capell packages on compatible v4 releases: capell-app/admin, capell-app/frontend, capell-app/navigation, capell-app/publishing-studio.
  • Run migrations before opening package resources or public routes.
  • Review package configuration before production-like verification: config/capell-events.php.
  • Review middleware, throttling, signatures, and public-output safety in routes/web.php before exposing routes.
  • Register the host scheduler so these declared commands run at their documented frequencies: Capell\Events\Manifest\EventsScheduleContribution (everyFifteenMinutes), Capell\Events\Manifest\EventsScheduleContribution (everyMinute).
  • Keep public Blade and cached HTML free of authoring markers, model IDs, permissions, signed editor URLs, and lazy database queries.
  • Custom write integrations must preserve invalidation for events cache tags.

Troubleshooting

Section titled “Troubleshooting”
Symptom Likely cause Check Fix
Package surface is missing after install Provider or manifest is not loaded Confirm capell.json, package composer.json, and provider registration Reinstall the package, refresh Composer autoload, and clear host caches
Admin screen or command fails on missing table Package migrations have not run Check the tables listed in Data Model Run host migrations and rerun the focused package test
Route returns unexpected output Route cache, middleware, or signed URL setup does not match the package route file Check the route files listed in Technical Shape Clear route cache and verify middleware before exposing public routes
Background work does not run Queue worker or declared schedule is not active Check the jobs and scheduled commands listed in Technical Shape Start the queue worker or host scheduler, then run the focused command or package test
Public output leaks unexpected state Render data, cache variation, or authoring boundary has regressed Check public Blade, cache tags, and public-output safety tests Move data loading out of Blade and rerun the package public-output tests

Quick Start

Section titled “Quick Start”
  1. Install the package: composer require capell-app/events.
  2. Run the required setup: php artisan capell:events-install.
  3. Open the Events index and confirm the admin workflow loads.

Next Steps

Section titled “Next Steps”