Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fortify::$registersRoutes always return false #6631

Closed
MattiaMarchiorato opened this issue Dec 20, 2024 · 2 comments
Closed

Fortify::$registersRoutes always return false #6631

MattiaMarchiorato opened this issue Dec 20, 2024 · 2 comments
Labels
needs more info More information is required

Comments

@MattiaMarchiorato
Copy link

Fortify Version

1.25.1

Laravel Version

11

PHP Version

8.3

Database Driver & Version

sail83 with mysql

Description

In our application we were using Fortify::ignoreRoutes(); in FortifyServiceProvider. Due to some upgrade, we tried to use the standard Fortify routes but, deleting the Fortify::ignoreRoutes(); the register and the others default routes were not working. After an investigation, we notice that Fortify::$registersRoutes is returning false.

Someone have ideas why?

Thanks

Steps To Reproduce

We tried with laravel 11 clean installation, and we don't notice the issue, we can't reproduce it.

@MattiaMarchiorato
Copy link
Author

We notice that in the config/app.php inverting the order of NovaServiceProvider and FortifyServiceProvider putting first FortifyServiceProvider is working properly.

App\Providers\TelescopeServiceProvider::class,
App\Providers\FortifyServiceProvider::class,
App\Providers\NovaServiceProvider::class,
App\Providers\JetstreamServiceProvider::class,

@crynobone crynobone transferred this issue from laravel/fortify Dec 23, 2024
@crynobone
Copy link
Member

I believe this related to #6619 (comment)

@crynobone crynobone added the needs more info More information is required label Dec 23, 2024
@laravel laravel locked and limited conversation to collaborators Dec 23, 2024
@crynobone crynobone converted this issue into discussion #6633 Dec 23, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
needs more info More information is required
Projects
None yet
Development

No branches or pull requests

2 participants