- How do I install alexjustesen/filament-spatie-laravel-activitylog in a Laravel app?
- Install it with Composer, register the plugin on your Filament panel, and ensure the activity_log table is migrated and populated by spatie/laravel-activitylog. There are no service providers to wire by hand and no significant config surface, so onboarding is usually measured in hours for a developer already fluent in Filament.
- Does this package support Filament v3 and Laravel 10?
- Yes, v0.7.0 adds Filament v3 support, which moves the package to a modern PHP and Laravel baseline of PHP 8.1+ and Laravel 10+. Verify the exact composer.json constraints for filament/filament, PHP, and Laravel before committing, because the release notes do not spell them out.
- Will alexjustesen/filament-spatie-laravel-activitylog work with Filament v2?
- The v0.7.0 release notes only say Filament v3 support and do not state whether Filament v2 support was dropped. If you are pinned to Filament v2, do not take v0.7.0 blindly; stay on v0.6.3 or verify composer.json constraints first.
- Do I need spatie/laravel-activitylog installed separately for this Filament plugin?
- Yes. This package is a presentation layer that surfaces records from spatie/laravel-activitylog; it does not own the schema or the write path. You still need Spatie Activity Log installed and configured, with the activity_log table migrated and populated.
- Can I customize the activity log table, filters, and detail views in Filament?
- The package includes customizable tables, filters, and detail views out of the box, and because it is a thin Filament resource you can override the resource, views, or config as needed. When upgrading, check for breaking changes to published views, resource classes, or config keys you may have overridden.
- Is this package safe for production audit logging?
- The package does not write audit data; Spatie Activity Log writes the activity_log rows, so the worst case for this plugin is a broken admin page rather than corrupted audit records. The real risks are pre-1.0 versioning, a single primary maintainer, and no stated support window, so treat releases as potentially breaking until 1.0.
- Does it support multi-tenancy and authorization policies for activity logs?
- The technical assessment flags per-tenant log scoping and policy-gated visibility as open questions, not confirmed features. You should verify the resource's tenancy and authorization hooks in a spike, and expect to customize the Filament resource if you need strict per-tenant or policy-based visibility.
- How does the plugin handle high-volume activity logs, pagination, and retention?
- Pagination and filtering are part of the Filament resource UI, but retention and pruning expectations are not documented in the provided context. For high-volume logs you likely own retention and pruning through Spatie Activity Log or database maintenance, so plan that before relying on the admin page.
- What are the alternatives to this package if I am not using Filament?
- If you are not on Filament, or your audit strategy is event-sourced or custom, this package has no role. The main alternative is hand-rolling a Filament resource over Spatie Activity Log, which the assessment estimates at roughly one to two days and keeps coupling low.
- Is alexjustesen/filament-spatie-laravel-activitylog actively maintained and is there a 1.0 roadmap?
- The assessment describes a single primary maintainer, low commit volume, and one first-time contributor on the critical Filament v3 PR. There is no stated support window or 1.0 roadmap in the context, so treat it as a best-effort side project with a small, non-critical surface that limits downside but does not remove sustainability risk.