Weave Code
Activity Timeline Laravel Package
lara-zeus/activity-timeline
A Laravel/Filament package from Lara Zeus that adds a clean activity timeline to your admin panel, making it easy to display, browse, and review model or user activity in chronological order. Simple to install and customize.
Add timelines to custom pages or infolist entries effortlessly. Plus, it teams up smoothly with Spatie Activitylog for easy tracking.
Frequently asked questions about Activity Timeline
- What is lara-zeus/activity-timeline used for?
- It is a Lara Zeus Filament v5 plugin that renders Spatie Activitylog records as a clean, chronological activity timeline inside your admin panel. You can drop it into a resource View page, an infolist entry, a relation manager, or a custom page. It is purely a presentation layer, not an audit or event-storage system, so the underlying data lives in Spatie's activity_log table.
- How do I install lara-zeus/activity-timeline in a Laravel app?
- Install the plugin and Spatie Activitylog with Composer (composer require lara-zeus/activity-timeline spatie/laravel-activitylog), then publish and run the Activitylog migration to create the activity_log table. Optionally publish the plugin config and views if you plan to theme it, run filament:assets, and register the plugin on your panel provider. Finally, add the LogsActivity trait and a getActivitylogOptions() method to the models you want to track.
- Does lara-zeus/activity-timeline require spatie/laravel-activitylog?
- Yes. The plugin is a UI on top of Spatie Activitylog and reads from the activity_log table, so adopting it means committing to Spatie's event schema as your event store. It does not provide its own logging engine or event capture. If you need a bespoke event schema or compliance-grade evidentiary audit records, this package is not the right fit.
- Which Laravel, PHP, and Filament versions does activity-timeline support?
- The current 5.x release line targets Filament v5, so your Laravel and PHP versions must satisfy Filament v5's own requirements. Release 5.0.3 bumps the filament/filament dependency to the 5.7.0 line, so keep your panel and the plugin on the same Filament minor to avoid view-internals drift. Always check composer.json on the repository before upgrading your panel.
- Where can I display the activity timeline in Filament?
- The timeline can be placed on a resource View page, as an infolist entry, inside a relation manager, or on a custom Filament page. That makes it useful for order, ticket, and account history tabs, ops change feeds, and internal recent-activity widgets. It is aimed at back-office Filament panels rather than customer-facing or API-only surfaces.
- Does lara-zeus/activity-timeline ship its own database migrations?
- No. The activity_log table is entirely inherited from spatie/laravel-activitylog, and you publish and run that package's migration yourself. The plugin adds only the Filament presentation layer on top. That also means it never prunes or archives the table for you, so retention is your responsibility.
- How do I start logging activity on a model so the timeline has data?
- Add Spatie's LogsActivity trait to the model and implement getActivitylogOptions() to declare what should be logged. Use logOnly() and dontLogEmptyChanges() to control field-level noise and keep the timeline readable. This logging policy is the genuinely non-trivial part of adoption because it is a product and data-governance decision, not an engineering step.
- How do I customize the look of the timeline, and what is the compact density option?
- You can publish the plugin's config and Blade views to change markup and styling, then run filament:assets if you touch assets. Release 5.0.3 added a compact density option for tighter timelines, alongside documentation and CI housekeeping. Because the 5.0.3 release is a patch with no migrations or breaking changes, adding it to an existing 5.x install should be low risk.
- What are the performance concerns on a large activity_log table?
- The plugin does not prune the activity_log table, so row counts grow without bound and query cost grows with them. Check the pagination defaults and confirm your causer and subject relations are eager-loaded, and make sure you have indexes on subject_type and subject_id plus created_at for chronological ordering. For high-volume tables, plan a retention or archiving job outside the package.
- Is lara-zeus/activity-timeline production ready and well maintained?
- The plugin code itself is small and low risk, and MIT licensing removes legal friction, but the project has a very small footprint: roughly 10 stars, no dependents, and a single-maintainer cadence dominated by chores and Dependabot updates. Treat continuity and issue-response cadence as adoption risks rather than functional ones, and pin your Filament minor. A scoped pilot on one high-value resource is a realistic way to validate it in a day or two.
Weaver
How can I help you explore Laravel packages today?