tappnetwork / filament-authentication-log Goto Github PK

Is the package being maintained and will it receive support for Laravel 11?

I'm using Laravel 11 and Filament v3.

$ sail composer require tapp/filament-authentication-log
./composer.json has been updated
Running composer update tapp/filament-authentication-log
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - tapp/filament-authentication-log[v3.0.0, ..., v3.0.3] require rappasoft/laravel-authentication-log ^3.0 -> satisfiable by rappasoft/laravel-authentication-log[v3.0.0].
    - tapp/filament-authentication-log v2.0.0 requires filament/filament ^2.0 -> found filament/filament[v2.5.3, ..., v2.17.55] but it conflicts with your root composer.json require (^3.2).
    - rappasoft/laravel-authentication-log v3.0.0 requires illuminate/contracts ^10.0 -> found illuminate/contracts[v10.0.0, ..., v10.48.4] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires tapp/filament-authentication-log * -> satisfiable by tapp/filament-authentication-log[v2.0.0, v3.0.0, v3.0.1, v3.0.2, v3.0.3].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require tapp/filament-authentication-log:*" to figure out if any version is installable, or "composer require tapp/filament-authentication-log:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Thanks for your work.

Please make navigation group configurable so i can group with other resources

I have followed every instruction and I have the table.

I have logged in several times with different browser, still the table is empty, as a result the Authentication Logs page is showing empty.

hi

i have overridden you resource class and i want to use getEloquentQuery to filter the results but i didn't had any luck. can you be so kind as to post a example on how to do that ?

Hello. I've followed the installation instructions in both laravel-auth-log and this one yet it's not appearing in my side bar.

Do I have to create a resource for it?

When logging in or signing out I get the error "Call to undefined method App\Models\User::authentications()".

I have installed your package and works great, however I can't find a way to hide the section or block users that has a role with no permissions to handle that resource.

I don't have to do anything special for the sections that I build myself, I create a new resource and with the Shield plugin I can assign to a role the permissions to be able to create, view, edit, etc. that resource. Just by doing that the left menu item shows or not depending on the role, however with your plugin it seems to ignore these rules.

Is there anything else I need to do?

Base table or view not found: 1146 Table 'db.authentication_log' doesn't exist

I create my own AuthenticationLogResource and extends Tapp\FilamentAuthenticationLog\Resources\AuthenticationLogResource
I need to override getEloquentQuery on resource but not work. how I can custom query AuthenticationLogResource ? Please help.

thank you.

After click on admin panel link authentication-logs get:

Symfony \Component \Routing \Exception\RouteNotFoundException
Route [filament.admin.resources.users.edit] not defined.

$response = $kernel->handle(
$request = Request::capture()
)->send();

Tapp\FilamentAuthenticationLog\Resources\AuthenticationLogResource: 83
Tapp\FilamentAuthenticationLog\Resources{closure}

Tapp\FilamentAuthenticationLog\Resources\AuthenticationLogResource 83 line:

return new HtmlString('<a href="'.route('filament.'.Filament::getCurrentPanel()->getId().'.resources.'.Str::plural((Str::lower(class_basename($record->authenticatable::class)))).'.edit', ['record' => $record->authenticatable_id]).'" class="inline-flex items-center justify-center hover:underline focus:outline-none focus:underline filament-tables-link text-primary-600 hover:text-primary-500 text-sm font-medium filament-tables-link-action">'.class_basename($record->authenticatable::class).'</a>');

Hi there,

I got an issue where if you move the default user model into another directory it will result in the Route [filament.admin.resources.users.edit] not defined. error.

After digging into the package, I found that that the issue lies in the file vendor\tapp\filament-authentication-log\src\Resources\AuthenticationLogResource.php, particularly at line 77. The code at this line only extracts the class name without considering the model's location. Consequently, this approach generates an incorrect route.

In my project, I moved both the user model and the Filament user resource to the Management directory, assigning the namespaces as follows: App\Models\Management and App\Filament\Resources\Management.

Temporary Workaround:

use App\Models\Management\User;

class UserResource extends Resource
{
    protected static ?string $model = User::class;
    protected static ?string $slug = 'users'; // remove 'management' from the slug
...

A possible fix for this issue:

1. Take anything after Models
2. Replace the remaining slashes with a dot
3. Do the original string manipulation

$authenticatable = Str::replace('\\', '.', Str::after($record->authenticatable::class, 'Models\\'));
$authenticatable = Str::plural(Str::lower($authenticatable));

return new HtmlString('<a href="'.route('filament.admin.resources.'.$authenticatable.'.edit', ['record' => $record->authenticatable_id]).'" class="inline-flex items-center justify-center text-sm font-medium hover:underline focus:outline-none focus:underline filament-tables-link text-primary-600 hover:text-primary-500 filament-tables-link-action">'.class_basename($record->authenticatable::class).'</a>');