We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I disable all the features within the fortify.php configuration file
fortify.php
'features' => [ // ],
the default Fortify routes are disabled, but the password confirmation route is still enabled. Is this a bug, or is it intentionally defined that way?
password confirmation route
laraven new app
composer require laravel/fortify
php artisan vendor:publish --provider="Laravel\Fortify\FortifyServiceProvider"
config/fortify.php
features
php artisan route:list
I think there should be a conditional that groups these routes in the routes.php file.
routes.php
fortify/routes/routes.php
Lines 95 to 104 in 77bd46a
The text was updated successfully, but these errors were encountered:
Make sure you've cached your config and routes after making those changes.
php artisan config:cache Then: php artisan route:cache
php artisan config:cache
php artisan route:cache
Sorry, something went wrong.
Sounds like a feature request. Feel free to PR something 👍
No branches or pull requests
Description:
When I disable all the features within the
fortify.php
configuration filethe default Fortify routes are disabled, but the
password confirmation route
is still enabled. Is this a bug, or is it intentionally defined that way?Steps To Reproduce:
laraven new app
composer require laravel/fortify
php artisan vendor:publish --provider="Laravel\Fortify\FortifyServiceProvider"
config/fortify.php
and remove all keys withinfeatures
arrayphp artisan route:list
I think there should be a conditional that groups these routes in the
routes.php
file.fortify/routes/routes.php
Lines 95 to 104 in 77bd46a
The text was updated successfully, but these errors were encountered: