search

filamentphp / filament

A collection of beautiful full-stack components for Laravel. The perfect starting point for your next app. Using Livewire, Alpine.js and Tailwind CSS.
https://filamentphp.com
MIT License
19.3k stars 2.96k forks source link

https://github.com/filamentphp/filamentphp.com #7726

Closed jamesautodude closed 1 year ago

jamesautodude commented 1 year ago

Package

filament/filament

Package Version

v3.0

Laravel Version

v10.0

Livewire Version

No response

PHP Version

v8.2.7

Problem description

When you change a user's password either through the database directly, or through CRUD (inside of Filament), that user will then be taken to an error of "Route [login] not defined"

When they refresh the page it takes them to the login page like normal

The URL is correct (project.com/admin) when this occurs, but for some reason they have to refresh that URL to get the login page

This seems to be an error where the password doesn't match anymore so the system tries to "kick" the user, but fails to direct to the proper route. If you manually set the login route to "/admin" in web.php, this error never happens. But then you can't set this route for other panels (/user, /app, /owner, etc)

Expected behavior

When changing a user's password, they should either stay logged in, or get kicked to the actual login page for the specific panel

Steps to reproduce

Change the user's password in database or through CRUD and then refresh the user's panel (or click on a page/link, like Dashboard)

Reproduction repository

https://github.com/filamentphp/filamentphp.com

Relevant log output

No response

github-actions[bot] commented 1 year ago

Hey @jamesautodude! We're sorry to hear that you've hit this issue. 💛

However, it looks like you forgot to fill in the reproduction repository URL. Can you edit your original post and then we'll look at your issue?

We need a public GitHub repository which contains a Laravel app with the minimal amount of Filament code to reproduce the problem. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private / confidential, since we want a link to a separate, isolated reproduction. That would allow us to download it and review your bug much easier, so it can be fixed quicker. Please make sure to include a database seeder with everything we need to set the app up quickly.