- What is wg-vn/laravel-activitylog-ui used for?
- It provides a modern web interface for Spatie's laravel-activitylog package inside Laravel applications. You use it to browse, filter, and analyze recorded activity without building your own dashboard. It adds analytics and real-time features on top of the underlying activity data.
- How do I install wg-vn/laravel-activitylog-ui in a Laravel app?
- Install it with Composer using composer require wg-vn/laravel-activitylog-ui. You should already have spatie/laravel-activitylog installed and its migrations run so activity records exist. Then publish the package config and assets if required by the README, and visit the provided UI route.
- Does this package require spatie/laravel-activitylog?
- Yes, it is a UI layer for Spatie's Activity Log, so the core spatie/laravel-activitylog package must be installed and logging activity. The UI reads from the activity table that Spatie's package creates. Without that data, the dashboard will have nothing to display.
- Which Laravel versions are supported by wg-vn/laravel-activitylog-ui?
- The package is built for Laravel applications and is intended to work with supported Laravel releases. Because version constraints can change between package releases, check the composer.json on GitHub or Packagist for the exact Laravel and PHP requirements. That is the safest way to confirm compatibility for your project.
- How do I secure the activity log UI in production?
- You should protect the UI routes with authentication and authorization middleware, such as auth and a gate or policy. Activity logs can contain sensitive model changes, user identifiers, and request context, so do not expose the dashboard publicly. Publish the package config and restrict access through the route middleware options.
- Can I filter activity logs by causer, subject, event, or date?
- Yes, the package advertises advanced filtering as a core feature. You can use the UI to narrow activity records by common dimensions such as the user who caused the activity, the affected model, the event name, and time range. This makes it easier to investigate changes without writing custom queries.
- Does wg-vn/laravel-activitylog-ui support real-time activity updates?
- The package description includes real-time features, so the dashboard can update as new activity is recorded. Real-time behavior in Laravel typically depends on broadcasting configuration, so review the README for any queue or broadcast driver requirements. If real-time is not needed, the standard activity view should still work.
- How do I customize the route prefix or middleware for the activity log UI?
- Publish the package configuration file and adjust the route prefix, middleware, and related UI options there. This lets you mount the dashboard under a private path and apply your application's auth or admin middleware. After changing config, clear cached config with php artisan config:clear.
- Why are no activities showing in the wg-vn/laravel-activitylog-ui dashboard?
- First confirm that spatie/laravel-activitylog is installed, migrated, and actively logging changes in your models. Then check that the UI route is using the correct database connection and that your middleware allows access. Also clear cached routes and config with php artisan route:clear and php artisan config:clear.
- What are alternatives to wg-vn/laravel-activitylog-ui for viewing Laravel activity logs?
- Alternatives include building custom Blade views or Filament resources on top of spatie/laravel-activitylog, or using broader admin tools such as Laravel Nova. This package is a focused, lightweight UI specifically for Spatie's activity data, so it avoids the overhead of a full admin panel. Compare the filtering, analytics, and real-time features against your actual needs.