-
Notifications
You must be signed in to change notification settings - Fork 75
Laravel 5.2 #23
Comments
Hi @XavRsl, This change means that you're going to use an abstract class than a concrete one. |
The change is to be made in the package if you don't want an error to be thrown. I just saw that after updating to 5.2. |
It's a good change, because its decouple the code from the dependency and we can extend the Guard with a custom one. |
Yep ! Le jeu. 24 déc. 2015 à 16:53, ARCANEDEV notifications@github.com a écrit :
|
Hi, Guard problem fixed for laravel 5.2 |
Hi, I have this problem: FatalErrorException in Model.php line 852: The problem is at the model, relationship: return $this->belongsTo(Config::get('auth.model'), 'user_id'); Thanks! |
I found the solution: in 'public function user()' change: return $this->belongsTo(Config::get('auth.model'), 'user_id');
|
Version 2.3.0 of the package is compatible with L5.2 |
Hi,
The path to Guard changed in Laravel 5.2 from
Illuminate\Auth\Guard;
toIlluminate\Contracts\Auth\Guard;
. This will need to be updated in ActivitylogSupervisor.phpThanks,
Xavier
The text was updated successfully, but these errors were encountered: