Ответ 1
Убедитесь, что ваш config/auth.php обновлен, если вы обновили его с 5.1.x до 5.2.
https://github.com/laravel/laravel/blob/v5.2.0/config/auth.php
Я начинаю и начинаю учиться и писать с laravel... Чтобы включить регистрацию входа в систему, я пишу это (как я вижу на одном tutorilal):
на routes.php
Route::controllers([
'auth'=>'Auth\AuthController',
'password'=>'Auth\PasswordController', ]);
и теперь, когда я печатаю: http://localhost:8888/auth/login Я получаю сообщение об ошибке:
InvalidArgumentException в строке AuthManager.php 71: Auth guard [] является не определено.
Также в папке просмотра нет файлов auth и файлов login.blade.php и других.
Убедитесь, что ваш config/auth.php обновлен, если вы обновили его с 5.1.x до 5.2.
https://github.com/laravel/laravel/blob/v5.2.0/config/auth.php
Это может быть проблемой в файле config/auth.php, где массив "defaults" устанавливает несуществующий защитник на Laravel 5.2.
В случае, если вы отредактировали свой config/auth.php
, например. чтобы добавить еще один защитник, и ваша конфигурация кэширована, ваши охранники не могут быть перезагружены. Если у вас возникла эта проблема, очистка конфигурации исправит ее.
$php artisan config:clear
или $php artisan config:cache
Я использую laravel 5.5
каталог программ App/config/Auth.php
<?php
return [
/*
|--------------------------------------------------------------------------
| Authentication Defaults
|--------------------------------------------------------------------------
|
| This option controls the default authentication "guard" and password
| reset options for your application. You may change these defaults
| as required, but they're a perfect start for most applications.
|
*/
'defaults' => [
'guard' => 'web',
'passwords' => 'users',
],
/*
|--------------------------------------------------------------------------
| Authentication Guards
|--------------------------------------------------------------------------
|
| Next, you may define every authentication guard for your application.
| Of course, a great default configuration has been defined for you
| here which uses session storage and the Eloquent user provider.
|
| All authentication drivers have a user provider. This defines how the
| users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user data.
|
| Supported: "session", "token"
|
*/
'guards' => [
'web' => [
'driver' => 'session',
'provider' => 'users',
],
'api' => [
'driver' => 'token',
'provider' => 'users',
],
// define your Auth here..
'your_auth_name' => [
'driver' => 'session',
'provider' => 'your table name',
],
],
/*
|--------------------------------------------------------------------------
| User Providers
|--------------------------------------------------------------------------
|
| All authentication drivers have a user provider. This defines how the
| users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user data.
|
| If you have multiple user tables or models you may configure multiple
| sources which represent each model / table. These sources may then
| be assigned to any extra authentication guards you have defined.
|
| Supported: "database", "eloquent"
|
*/
'providers' => [
'users' => [
'driver' => 'eloquent',
'model' => App\User::class,
],
// 'users' => [
// 'driver' => 'database',
// 'table' => 'users',
// ],
// add provider to your auth
'table name' => [
'driver' => 'eloquent',
'model' => App\User::class,
],
// **'model' => App\User::class,**
// here App\User is model so you have to generate own model using **php artisan make:model Model_name**
],
/*
|--------------------------------------------------------------------------
| Resetting Passwords
|--------------------------------------------------------------------------
|
| Here you may set the options for resetting passwords including the view
| that is your password reset e-mail. You may also set the name of the
| table that maintains all of the reset tokens for your application.
|
| You may specify multiple password reset configurations if you have more
| than one user table or model in the application and you want to have
| separate password reset settings based on the specific user types.
|
| The expire time is the number of minutes that the reset token should be
| considered valid. This security feature keeps tokens short-lived so
| they have less time to be guessed. You may change this as needed.
|
*/
'passwords' => [
'users' => [
'provider' => 'users',
'email' => 'auth.emails.password',
'table' => 'password_resets',
'expire' => 60,
],
], ];