- What is sashalenz/nova-activitylog used for?
- It is a Laravel Nova tool that acts as a presentation layer over spatie/laravel-activitylog, letting you browse, filter, and inspect recorded model events and user actions inside your admin panel. It does not introduce a second audit pipeline, because Spatie's activity_log table and model remain the source of truth. Typical uses are support triage, compliance-adjacent change history, and debugging who changed a specific record.
- How do I install sashalenz/nova-activitylog?
- Install it with Composer alongside Laravel Nova and spatie/laravel-activitylog, then register the tool in your NovaServiceProvider and publish any provided config or assets as the README instructs. For a team already on Nova, expect hours of effort rather than sprints. The real cost driver is usually data: existing activity_log volume, causer and subject morph mapping, and retention policy.
- Does nova-activitylog require spatie/laravel-activitylog?
- Yes. It is a thin UI layer and will not work as a standalone audit solution. You must already use Spatie's package, or be willing to adopt it, because the activity_log table and Activity model remain the source of truth. Nova only reads and queries those records.
- Which Laravel, PHP and Nova versions does version 2.0.0 support?
- The supplied release data does not confirm the constraint set, so check the composer.json in the 1.1.1 to 2.0.0 diff before upgrading. The most likely breaking axes for a package of this shape are a Nova major-version requirement, a raised PHP or Laravel floor, or renamed tool and field classes and config keys. Determine the Nova constraint first, because it decides whether the upgrade is a one-hour or one-quarter item.
- How do I show an activity timeline on a Nova resource?
- The package exposes activity records as a Nova tool or resource and, where relevant, a field you can attach to existing Nova resources. Attach the field to the resources you want to audit and confirm that rendering, filtering, and pagination behave correctly. Smoke-test against seeded activity data before merging.
- Is upgrading from 1.1.1 to 2.0.0 a breaking change?
- It is a major version bump with no substantive release notes beyond an auto-generated changelog compare link, so under semver you should assume breaking changes and verify them yourself. Read the 1.1.1 to 2.0.0 diff and the new composer.json before touching code. Do not upgrade blind in place; branch the upgrade and pin to 1.1.1 on your current branch as a rollback.
- How do I safely upgrade nova-activitylog to 2.0.0?
- Pin to 1.1.1 on your current branch, read the diff and new composer.json, then upgrade in a disposable environment with composer update sashalenz/nova-activitylog --with-dependencies and inspect the lockfile delta. Diff any published config and assets against the new defaults and re-publish only deliberately. Smoke-test the tool against seeded activity data before merging.
- Can I filter activity logs by causer, subject or event in Nova?
- Yes, filtering and inspecting recorded events and user actions is the core purpose of the Nova resource surface. Filtering and pagination defaults may have changed in 2.0.0, so validate them against representative data volume. Causer and subject resolution depends on how your morph map is configured in Spatie's package.
- Does nova-activitylog create its own database tables or migrations?
- No, it does not introduce a second audit pipeline; records live in Spatie's existing activity_log table. Whether 2.0.0 changes schema expectations or requires re-publishing migrations and assets is not confirmed by the release data, so check the diff before upgrading. If migrations are published, review them rather than blindly republishing.
- Is sashalenz/nova-activitylog actively maintained, and what are the alternatives?
- It is a single-author package, so weigh the maintainer bus factor carefully for a long-lived audit surface. Commit cadence, issue responsiveness, and an explicit Nova 5 compatibility statement should all be checked before committing. If you need stronger support guarantees, evaluate first-party Nova audit tooling or build the read surface in-house over Spatie's activity data.