z3d0x / filament-logger

Extensible activity logger for filament that works out-of-the-box.

Hi 👋 I'm ZedoX

Full-Stack Web Developer

I started my web development journey in late 2020. After quickly picking up HTML & CSS, I moved on to learn PHP it's most popular framework, Laravel. Somewhere along the way I also picked up JavaScript & React as well.

Thesedays I mainly work with Laravel. TALL stack (Tailwind, Alpine.js, Laravel, Livewire) to be specific. You may also see me occasionally contributing to open-source projects or hanging around in the Filament Community

Socials

Badges

My GitHub Stats

Top Repositories

filament-logger's Issues

Old props not being saved in properties column

Hello,

Whenever I update a model, old properties are not being saved in the activity log. Is there an option to activate this feature?

Thank you!

In laravel 11 menu Activity Log not effect

I use laravel 11 and i use shield for permission, i success generate ActivityPolicy but not effect.

this AuthServiceProvider

this regis AuthServiceProvider

and this ActivityPolicy

i try to check Users menu and effect but after try Activity menu not effect

Table row disabling clickable not working

I cannot make the table row to be NOT CLICKABLE

This link https://filamentphp.com/docs/2.x/tables/getting-started#disabling-clickable-rows cannot applied

Unable to locate a class or view for component [filament-logger::filament-logger.nav.log.icon].

After installing the package, I got this error when navigation to /admin.

"Unable to locate a class or view for component [filament-logger::filament-logger.nav.log.icon]."

'filament/filament': v2.16.55
'spatie/laravel-activitylog': 4.7.2
'z3d0x/filament-logger': v0.4.1

Translation not translate in filter

The translation key is available, but it is not translate data inside filter (Old and New)

And also provide "Can be key or value" translation key

Logger Error When Use Command php artisan migrate:fresh --seed

Hallo.
first of all, I've installed this plugin, and it's really amazing. thank you for making this plugin 👍.

back on topic, I ran the migration using this command php artisan migrate:fresh --seed. the migration ran successfully, but the seeder didn't run correctly and crashed my mysql..

Then I ran the migration & seed commands separately. strangely the migration command ran fine. but not the seeder.

So, the alternative path I chose. set all the key enabled to false

dan itu berjalan lancar tanpa crash.

menurut saya, masalahnya adalah karena saya menggunakan terminal

harap Anda segera memperbaikinya.Halo.
pertama-tama, saya sudah menginstal plugin ini, dan ini sangat menakjubkan. terima kasih telah membuat plugin ini 👍.

kembali ke topik, saya menjalankan migrasi menggunakan perintah ini php artisanmigrate:fresh --seed. migrasi berhasil dijalankan, tetapi seeder tidak dapat berjalan dengan benar dan membuat mysql saya crash.

Kemudian saya menjalankan perintah migrasi & seed secara terpisah. anehnya perintah migrasi berjalan dengan baik. tapi tidak dengan seeder.

jadi, jalan alternatif yang saya pilih. disetel semua kunci diaktifkan ke false

and it ran smoothly without any crashes.

i think, the problem is that I'm using the terminal.

My hope is that you will want to fix this.
thanks

migration error

Hi, it looks like the database tables need to be created for using this plugin - but there's no info on how to generate the migration templates. Any help? Thanks!

getLoggableAttributes() error on delete method

Good day,

I am able to process all other methods and log events such as create and update. Up until two days ago, I was able to delete as well. Now when I delete a resource I get the following error:

Z3d0X\FilamentLogger\Loggers\AbstractModelLogger::getLoggableAttributes(): Argument #2 ($values) must be of type array, null given, called in /app/vendor/z3d0x/filament-logger/src/Loggers/AbstractModelLogger.php on line 69

Custom theme colors don't work

When Filament is customized with a custom style and colors, the package doesn't account for them. That is, if my theme's color for danger is Tailwind's red, the package still accounts for the default theme color of gray or something.

I think listening to a FilamentServed event - if there is one - would help to identify if its $theme isn't null, and therefore would be injected as a style too.

Stop password from being logged?

How can I stop getting my passwords logged as a key/value pair in the properties?

show original values in the update event

is it possible to save/show the original values when an update event is recorded ?

Missing saved old value when update a resource

While testing the package functionalities, I noticed that the old values are missing when updating a resource. By this, I mean that in the spatie-activity log, when I update a resource, it saves the old values related to the new (changed) value. Is this feature missing from this package, or has it not been developed yet? I assume it might be a bug since this functionality is present in the base spatie activity log package.

Config customizations

First of all, thanks for this great plugin.

To use it I would need a couple of new features:

1. ability to log models who don't have a resource
2. ability to set another resource class

I can try to make a PR if you want (or I can fork :D)

sqlite database migration not working due to this plugin

it may have large amount of data to seed in the table that causes the seeding is unsuccessful, the error is allocated memory is not enough.

Event auto discovery not working anymore

It looks like Event Auto Discovery no longer works when your plugin is active. At least when php artisan event:cache is executed.

shouldDiscoverEvents from the EventServiceProvider of the framework always returns false.

Maybe I should mention that I run laravel with octane.

Filament v3 support?

Filament v3 has been released. Will you be supporting it?

Package not using the authentication guard setup in filament config

I have two authentication guards. The filament package is using a special admin one that uses a different table and model than the default users configured in laravel.
First thing i've noticed is that when i view an event in filament the user field is empty.

Second issue is after logging in with the regular auth guard. This package throws an error because it's trying to call some filament username function that obviously isn't defined on the regular Users model.

Here's a screenshot of the error.

For now, the quickest solution was to disable the access logger from the package config.
I can probably override the Logger and try and make it use only the admin guard but that would mean i'd have to override all the guards to properly get the username in all the other logs.

Bottom line, I think the package needs an update to read filament.auth.guard config value and apply that to all the logging.

Allow to integrate/use Filament shield for roles and Permission

Allow to add use HasPageShield; traits based on this documentation.

https://github.com/bezhanSalleh/filament-shield#pages

Mobile responsive in View Activity

The user and subject place in mobile view is not responsive:

make the activity logs searchable

hi, is there already an option for this?

My App no logger able to login after installing logger

In my app authentication done by shield. After installation of https://filamentphp.com/plugins/logger. Am not able to login any more. please someone save me from this sleepless night.

User context not shown in filament page but saved in db

I'm getting this issue where the user (causer_id) gets set while on the filament view i get nothing

EDIT: i noticed this is because I use a custom attribute for User's name, maybe this can be added as a custom config property?

Error: Data truncated for column 'subject_id' at row 1

I have installed the package filament-logget in my fresh laravel project. Then I have installed buildix/timex package. When I create, delete or update event on timex there is error from filament-logger. You can see it in screenshot.

I have created issue about it in for buildix/timex (buildix/timex#29) but I reived answer like:

"
Hello. Thank you.
I'm not sure that it refers to timex actually.

The error occurred because filament-logger (laravel logger) is using morphs and timex is using uuid - so it has to either timex database changes upon migration not to use uuid, or logger database adjustments to

$table->nullableUuidMorphs('taggable');
"

So can you help me fix the issue?

Thanks!

HTML tags is visible

activity-logs view page

Hero icon not found

Hi, thank you for this plugin!

I'm reporting an issue regarding the last version of the package (v0.6.0) with filament version (v3.0.30)

I'm getting Svg by name "o-clipboard-documents-list" from set "heroicons" not found. when loading the filament dashboard.

Cannot upgrade to Laravel 10

More of a FYI, upgrading to Laravel 10 introduces a dependency error

Problem 1
- Root composer.json requires laravel/framework ^10.0 -> satisfiable by laravel/framework[v10.0.0].
- z3d0x/filament-logger v0.4.2 requires illuminate/contracts ^8.0 | ^9.0 -> satisfiable by illuminate/contracts[v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.0].
- Only one of these can be installed: illuminate/contracts[v5.4.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.0, v10.0.0], laravel/framework[v10.0.0]. laravel/framework replaces illuminate/contracts and thus cannot coexist with it.

• Root composer.json requires z3d0x/filament-logger ^0.4.2 -> satisfiable by z3d0x/filament-logger[v0.4.2].