Laravel BadMethodCallException не найден метод моей модели - PullRequest
0 голосов
/ 31 марта 2020

По некоторым причинам я получаю ошибку при методе отношений DownloadHistorys () OneToMany: enter image description here Мои модели User и DumpDownloadHistory:

<?php

namespace App\Models;

use App\Models\DumpDownloadHistory;
use App\Models\Groups;
use Illuminate\Database\Eloquent\Model;


class User extends Model  {

    protected $fillable = ['email', 'full_name', 'name', 'mobile', 'phone', 'fax', 'downloadPrice', 'tokens', 'dailyDownloads', 'added_by', 'groups_id', 'status', 'user_about','admin_note', 'password', 'last_access', 'last_ip'];

    /**
     * The database table used by the model.
     *
     * @var string
     */
    protected $table = 'users';

    /**
     * The attributes excluded from the model's JSON form.
     *
     * @var array
     */
    protected $hidden = array('password', 'remember_token');

    public function downloadHistorys(){
        return $this->hasMany(DumpDownloadHistory::class);
    }

}
<?php

namespace App\Models;

use App\Models\User;

use Illuminate\Database\Eloquent\Model;

class DumpDownloadHistory extends Model
{
    protected $fillable = ['user_id', 'dataset', 'user_ip', 'downloadCost'];

    protected $table = 'dump_download_histories';

    protected $primaryKey = 'id';

    public function user(){
      return $this->belongsTo(User::class);
    }
}

Мои модели размещены в приложении Папка моделей. Я добавил свой экземпляр модели в контроллер. Я получаю сообщение об ошибке при попытке вызвать мои методы. Любая помощь будет полезна.

auth()->user()->downloadHistorys()->create([
                  'user_id' => auth()->user()->id,
                  'dataset' => $id,
                  'user_ip'=> request()->ip(),
                  'downloadCost' => auth()->user()->downloadPrice
                ]);

PS Я не использую построитель схем для базы данных. Я подключился к существующей базе данных MySQL.

Отредактировано

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's data.
    |
    | Supported: "session", "token"
    |
    */

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],

        'api' => [
            'driver' => 'token',
            'provider' => 'users',
            'hash' => false,
        ],
    ],

    /*
    |--------------------------------------------------------------------------
    | 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's 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',
        // ],
    ],

    /*
    |--------------------------------------------------------------------------
    | Resetting Passwords
    |--------------------------------------------------------------------------
    |
    | 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',
            'table' => 'password_resets',
            'expire' => 60,
        ],
    ],

];

1 Ответ

1 голос
/ 31 марта 2020

Похоже,

'providers' => [
    'users' => [
        'driver' => 'eloquent',
        'model' => App\User::class,
    ],
],

этот раздел неправильный. Если вы хотите использовать App \ Models \ User model в качестве аутентификации, измените модель на App \ Models \ User.


И измените свое приложение \ Модели \ Модель пользователя следующим образом

use Illuminate\Foundation\Auth\User as Authenticatable;

class User extends Authenticatable {}
Добро пожаловать на сайт PullRequest, где вы можете задавать вопросы и получать ответы от других членов сообщества.
...